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/06/17 14:04:38 UTC

[GitHub] [couchdb] nickva commented on issue #4066: Replicator giving issue , with jobs getting into crashed type

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

   It means the `_changes` feed connection is closed unexpectedly. If the error count is 0, it happens rarely enough that the error count is reset. So it's probably more rare than once a minute or so.
   
   A few things to try:
    * Check if you're using a restrictive replication filter.
    * Increase the replicator connection timeout configuration to say 90000(msec).
    * Check if your load balancer (if you have one), has an idle connection timer then bump that too and then, check that it's not set to buffer connection data.
   
   In general replicator will retry the replications on failure and continue where it left off. It's pretty resilient like that. So, if you don't want to track down the connection issues, and it seems your data replicates as intended you probably don't have to worry about it.


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