sergey-safarov opened a new issue, #5026: URL: https://github.com/apache/couchdb/issues/5026
## Description In my installation, in CouchDB logs messages I can see messages like ``` 1 conflicted shard in cluster ``` I have tried to delete old databases and in the server logs can see ``` [critical] 2024-03-26T17:28:24.081510Z [email protected] <0.16743.70> -------- 1 conflicted shard in cluster [critical] 2024-03-26T17:28:29.187245Z [email protected] <0.18085.70> -------- 1 conflicted shard in cluster [critical] 2024-03-26T17:28:34.311446Z [email protected] <0.21253.69> -------- 1 conflicted shard in cluster [critical] 2024-03-26T17:28:39.541320Z [email protected] <0.31584.67> -------- 1 conflicted shard in cluster [critical] 2024-03-26T17:28:44.649152Z [email protected] <0.20660.67> -------- 1 conflicted shard in cluster [critical] 2024-03-26T17:28:49.717562Z [email protected] <0.23910.70> -------- 1 conflicted shard in cluster [critical] 2024-03-26T17:28:54.921189Z [email protected] <0.9403.70> -------- 1 conflicted shard in cluster [critical] 2024-03-26T17:29:00.033066Z [email protected] <0.19084.68> -------- 1 conflicted shard in cluster [critical] 2024-03-26T17:29:05.174271Z [email protected] <0.25777.70> -------- 1 conflicted shard in cluster [critical] 2024-03-26T17:29:10.262848Z [email protected] <0.30249.69> -------- 1 conflicted shard in cluster [critical] 2024-03-26T17:29:15.402787Z [email protected] <0.27844.70> -------- 1 conflicted shard in cluster [critical] 2024-03-26T17:29:20.721704Z [email protected] <0.20999.70> -------- 1 conflicted shard in cluster [critical] 2024-03-26T17:29:25.680320Z [email protected] <0.100.70> -------- 1 conflicted shard in cluster [critical] 2024-03-26T17:29:30.777084Z [email protected] <0.243.71> -------- 1 conflicted shard in cluster [critical] 2024-03-26T17:29:35.905120Z [email protected] <0.23983.70> -------- 1 conflicted shard in cluster [critical] 2024-03-26T17:29:41.078100Z [email protected] <0.4260.71> -------- 1 conflicted shard in cluster [critical] 2024-03-26T17:29:46.252992Z [email protected] <0.5119.71> -------- 1 conflicted shard in cluster [critical] 2024-03-26T17:29:51.305345Z [email protected] <0.6351.71> -------- 1 conflicted shard in cluster [critical] 2024-03-26T17:29:56.444482Z [email protected] <0.6549.71> -------- 1 conflicted shard in cluster [critical] 2024-03-26T17:30:01.605705Z [email protected] <0.5639.61> -------- 1 conflicted shard in cluster [critical] 2024-03-26T17:30:06.766324Z [email protected] <0.9687.69> -------- 1 conflicted shard in cluster ``` These log messages do not provide information about: 1) database with conflicts; 2) shard file; 3) conflicted revision id. Could you extent logs message? ## Steps to Reproduce I do not know ## Expected Behaviour Log messages should allow identifying conflicted database, shard, and revision id. ## Your Environment [TIP]: # ( Include as many relevant details about your environment as possible. ) [TIP]: # ( You can paste the output of curl http://YOUR-COUCHDB:5984/ here. ) * CouchDB version used: ```json { "couchdb": "Welcome", "version": "3.3.3", "git_sha": "40afbcfc7", "uuid": "385419103339-esrp", "features": [ "access-ready", "partitioned", "pluggable-storage-engines", "reshard", "scheduler" ], "vendor": { "name": "The Apache Software Foundation" } } ``` * Browser name and version: Not used * Operating system and version: ``` NAME="CentOS Stream" VERSION="8" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="8" PLATFORM_ID="platform:el8" PRETTY_NAME="CentOS Stream 8" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:8" HOME_URL="https://centos.org/"; BUG_REPORT_URL="https://bugzilla.redhat.com/"; REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux 8" REDHAT_SUPPORT_PRODUCT_VERSION="CentOS Stream" ``` ## Additional Context [TIP]: # ( Add any other context about the problem here. ) -- 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]
