nickva commented on issue #5934:
URL: https://github.com/apache/couchdb/issues/5934#issuecomment-4344920644

   I think it could be a combination of:
   
   https://github.com/apache/couchdb/pull/5709
   
   and maybe 
   
   https://github.com/apache/couchdb/pull/5709
   
   In the first case we avoid creating checkpoints for invalid mrviews. This 
could mean views with no map functions or ddocs for non-mrview views (for 
example a clouseau doc previously would have also created an non-functional 
mrview purge checkpoint because we still managed to parse an #mrst{} record 
from it)
   
   But those would only help for newly created dbs. If you already have invalid 
checkpoint it won't auto-clean them
   
   It would also be interesting to see if those "stale" view design documents 
look like. To get purge the checkpoints you'd have to use something like 
`/test-db/_local_docs?include_system=true` but even then you may miss some as 
those are not clustered, maybe run that a few times or another way is to query 
5986 (node local) shards/ individual shards. Checkpoints do not directly refer 
to ddocs I believe so we may need to run through all the design documents check 
their `/_info` checkpoint and cross reference them with the signature from.
   
   > It looks like document already deleted but view does not track it about 
374 days (32383475 seconds).
   > {"error":"not_found","reason":"missing"} It looks like document already 
deleted but view does not track it about 374 days (32383475 seconds).
   
   That I think is a smoking gun there is something off with the view building 
in general. If you add a new document that should appear in the view to the db 
then query the view what happens? Any error or exceptions?
   


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