英文:
Aerospike scan returns with status "done (abandoned-response-timeout)"
问题
有时候我们的aerospike数据库返回的数据量比实际可用的数据量要少。在检查日志时，注意到以下条目：
INFO (scan): (scan.c:614) starting basic scan job {id} {namespace:set} priority 2, sample-pct 100
INFO (scan): (scan.c:692) finished basic scan job {id} (-2)
如果我们通过show scans检查扫描，我们会在表中看到以下条目：
trid: {id} | job-progress: 49.78 | job-type: basic | status: "done (abandoned-response-timeout)"
根据状态，我们遇到了超时问题，这就是为什么没有返回所有数据的原因。然而，在这种情况下，我们更希望收到错误消息而不是返回较少的数据。
我们正在使用三个aerospike节点/容器的aerospike版本3.15.1.4，并且我们正在使用go-client与Aerospike数据库进行交互。
有办法增加超时时间吗？
英文:
Sometimes less data is returned than is actually available in our aerospike database. When checking the logs, the following entries were noticed:
INFO (scan): (scan.c:614) starting basic scan job {id} {namespace:set} priority 2, sample-pct 100
INFO (scan): (scan.c:692) finished basic scan job {id} (-2)
If we check the scans via show scans, we see the following entry in the table:
trid: {id} | job-progress: 49.78 | job-type: basic | status: "done (abandoned-response-timeout)"
According to the status we are running into a timeout, which is why not all data is returned. In this case, however, we would rather expect an error message instead of less data being returned.
We are running aerospike version 3.15.1.4 with three aerospike nodes/pods. And we are using the go-client to interact with the Aerospike database.
Is there a way to increase the timeout?
答案1
得分: 2
Aerospike现在发布了5.6.0.9版本。请升级，并且您将需要经历中间版本的跳转才能到达最新版本，因此需要仔细计划。扫描功能已经进行了全面改进。引入了Set-index，可以显著加快对包含其他大型集合或大量记录的非常大的命名空间中记录数量很少的集合的扫描速度。
英文:
Aerospike is now at release 5.6.0.9. Upgrade please, and you will be going through intermediate jump versions to get to the latest, so need to carefully plan it out. Scans have been overhauled. Set-index has been introduced to really speed up scans on sets having a very small number of records in an otherwise very large namespace containing other large set or large number of records.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论