Details
-
Improvement
-
Resolution: Won't Fix
-
Major
-
7.6.0, 7.2.5
-
None
-
0
Description
We are disabling queryCleanupLostAttempts but observed that the cleanup is still taking place. And to make this parameter work, we need to restart the query service. But this is not mentioned in official doc.
So our questions are:
- Is this expect to restart Query service everytime we toggle queryCleanupLostAttempts parameter?
- If yes, then, can you please help us add this field into the settings config which can be picked without restart, as some of our tests are failing because of transaction getting cleaned up?
This is how our framework is working currently:
- enable/disable cleanup via rest call with param: queryCleanupLostAttempts
- restart query service using SSH (not supported in Capella) to make the 1 work
But since SSH is not supported in Capella, we are looking for an alternative to disable queryCleanupLostAttempts.
Server logs for your reference: http://supportal.couchbase.com/snapshot/120c0b35bbba38734526c966065be31f::1
Thanks!