1 個回答
- 最新
- 最多得票
- 最多評論
1
If you are receiving a timeout from Neptune when running a large query, such as the delete operation referenced here, then you can extend the timeout at the cluster level by changing the neptune_query_timeout
to a larger value. This will require a reboot of the cluster but modifying this value will change the global timeout and allow for longer running queries.
If you need additional help, I would suggest opening a support case if possible or if not, then please provide additional details on the error you are receiving here as well as a sample set of data to reproduce the issue if possible.
已回答 8 個月前
相關內容
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
Thankyou @ Dave-AWS for giving answer I will try increasing timeout limit .