nickva opened a new pull request, #5758:
URL: https://github.com/apache/couchdb/pull/5758
Previously `verify_purge_checkpoint/2` was returning `false` for valid purge
internal replicator clients becuase `mem3:shards(DbName)` threw a
`database_does_not_exist` error, since `mem3:shards(DbName)` works with cluster
db names not shard names.
This error leads to a valid internal replication client not being recognized
and so the purge infos cleanup could stall with invalid_purge_seq errors
thrown. The symptoms would be log error lines that look like the following:
```
Missing or stale purge doc
'_local/purge-mem3-1c8980f090d010a0570f69c22b216a2a-ef6642a7a3a78239f33b46ffdc600a81'
on <<"shards/50000000-5fffffff/.../bench_db_1762663269.1762663269">> with
purge_seq '2796726'
mfa: mem3_rpc:load_purge_infos_rpc/3
error:{invalid_start_purge_seq,2900788,3030215}
[
{couch_bt_engine,fold_purge_infos,5,[{file,"src/couch_bt_engine.erl"},{line,619}]},
{mem3_rpc,load_purge_infos_rpc,3,[{file,"src/mem3_rpc.erl"},{line,214}]},
{rexi_server,init_p,3,[{file,"src/rexi_server.erl"},{line,141}]}
]
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
