sergey-safarov commented on issue #5934:
URL: https://github.com/apache/couchdb/issues/5934#issuecomment-4524686594

   I have compiled rpm packages for for current master branch (commit 
a006a2ca161e4a82e6632247572f981c0de33037, for soem reason it reporting 3.5.1) 
and installed on servers.
   ```sh
   [ssafarov@esrp-0a ~]$ curl -s http://admin:[email protected]:5984| jq
   {
     "couchdb": "Welcome",
     "version": "3.5.1-a006a2c",
     "git_sha": "a006a2c",
     "uuid": "63d840e5b0823e4b275a71d25205d04c",
     "features": [
       "quickjs",
       "access-ready",
       "partitioned",
       "pluggable-storage-engines",
       "reshard",
       "scheduler"
     ],
     "vendor": {
       "name": "The Apache Software Foundation"
     }
   }
   ```
   During first seconds after start I see messages like
   ```
   mem3_rep : deleting inactive purge checkpoint 
shards/38000000-3fffffff/account/e2/41/f5926a230d6bb1488de0f3c37cc7.1776064622 
: 
_local/purge-mem3-23b49475b4082844d4b8ba06ab8964c0-ae267d1169b7e8dc5eaa983a9360008b
   ```
   Then I send command compact views
   ```sh
   curl  -s -X POST -H "Content-Type: application/json" 
http://admin:[email protected]:5984/test/_compact| jq
   ```
   And get in the couchdb logs same message
   ```
   couch_db : Purge checkpoint <<"shards/00000000-ffffffff/test.1768133824">> : 
_local/purge-mrview-6ca561964a095a15f145d0aac875a6da not updated in 11364129 
seconds. Expected update interval is at least 86400 seconds```
   
   > create new view with ddoc_new id then, let it build in the background then 
replace ddoc with ddoc_new in production all the clients would see the already 
built view)
   
   I have tested this method and it work in this case. This allow repair broken 
view.
   
   And I execute compact
   ```sh
   curl  -s -X POST -H "Content-Type: application/json" 
http://admin:[email protected]:5984/test/_compact| jq
   ```
   And do not see more "deleting inactive purge checkpoint shard" messages.


-- 
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]

Reply via email to