Nick Vatamaniuc

As far as db / doc not found, I think error reason is already provided: ``` % http $DB/mydb2/doc4 HTTP/1.1 404 Object Not Found { "error": "not_found", "reason": "Database does...

> Works only for normal docs, but for local docs (replication logs) it won't return anything. Right, local seq is the update seq of the document, so it won't be...

> I am not able to understand this, not an expert on this matter. Are you suggesting that few steps of replication can be combined onto a single connections ?...

@chewbranca good idea to have better priority classes! Replicator db access from the replicator could be a `system` db access or a have its own `replicator` class. But I can...

It looks there a view term which could not be opened and decompressed. I noticed you use `file_compression none` wonder if that has anything to do with it. Would there...

@jeydude makes sense. When you switched from snappy to `none`, that was the same database? In other words, snappy was used, db was filled with data, then compression was switched...

When the view is rebuilding it won't be able to return results. So make sure to account for that. At 280Gb that could take quite a while. First, apply `deflate_6`...

> send a `no_bytes_will_ever_be_requested` message to PARSER so it can decrement the workers it waits for? @janl Yeah, I wonder if that would work. And we'd explicitly check for `new_edits=false`...

That's a good test. If we run with `n=1` only mode for integration tests, there could be a separate issue revealed where we drop the connection and never close it...

I think this issue is fixed. Closing.