You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2022/07/13 19:40:10 UTC

[GitHub] [couchdb] chewbranca commented on issue #4101: Set io_priority in all IO paths

chewbranca commented on issue #4101:
URL: https://github.com/apache/couchdb/issues/4101#issuecomment-1183606198

   > Replicator db access from the replicator could be a system db access or a have its own replicator class. But I can see the user accessing db (user creating a replication doc) staying as an interactive request?
   
   Yeah I think `system` for the replicator db access would work fine.
   
   I do like the idea of being able to prioritize replicator traffic at a different priority level than `interactive`, I think that would be a useful addition allowing for replication traffic to be deprioritized a bit relative to normal interactive client requests. This would be a bigger change than just properly setting `io_priority` values in places where it's currently absent, as I believe for that to work we would need to do something like extrapolate from the http request user agent that it's `Couch-Replicator` and then propagate the `replication` io_priority from the coordinator node to all the rpc nodes.
   
   > I think that's just a left-over clause we didn't clean up when we removed the local access.
   
   Makes sense 👍 


-- 
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-unsubscribe@couchdb.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org