rnewson opened a new issue, #5528:
URL: https://github.com/apache/couchdb/issues/5528
## Description
when interactive_database_writes_threshold is exceeded, we deliberately
allow mem3_rep to continue internal sync (indeed all replicated change requests
are permitted). unfortunately mem3_rep will eventually crash when it tries to
write its checkpoint as this is a normal doc edit. Exempt these writes from the
blocking behaviour.
...with exit value:#012{{nocatch,{insufficient_storage,<<"database_dir is
too
full">>}},[{couch_db,update_doc,4,[{file,"src/couch_db.erl"},{line,876}]},{mem3_rep,update_locals,3,[{file,"src/mem3_rep.erl"},{line,740}]},{mem3_rep,replicate_batch,4,[{file,"src/mem3_rep.erl"},{line,641}]},{maps,map_1,3,[{file,"maps.erl"},{line,441}]},{maps,map,2,[{file,"maps.erl"},{line,426}]},{mem3_rep,replicate_batch_multi,1,[{file,"src/mem3_rep.erl"},{line,619}]},{mem3_rep,'-push_changes/1-fun-0-',3,[{file,"src/mem3_rep.erl"},{line,550}]},{mem3_rep,with_src_db,2,[{file,"src/mem3_rep.erl"},{line,840}]}]}#012
## Steps to Reproduce
enable disk_monitor, add lots of data then promptly set
interactive_database_writes_threshold to lower than current disk usage. with
luck internal sync is behind and will then fail to catch up when it tries to
checkpoint.
## Expected Behaviour
internal replication should proceed regardless of
interactive_database_writes_threshold setting, at least until the end of disk
itself is reached.
## Your Environment
N/A
## 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: notifications-unsubscr...@couchdb.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
