You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by rnewson <gi...@git.apache.org> on 2016/03/24 14:44:47 UTC

[GitHub] couchdb-couch-replicator pull request: restart replications on cra...

GitHub user rnewson opened a pull request:

    https://github.com/apache/couchdb-couch-replicator/pull/33

    restart replications on crash

    COUCHDB-2975 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cloudant/couchdb-couch-replicator 2975-restart-replications-on-crash

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-couch-replicator/pull/33.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #33
    
----
commit 73afc584bd10f68626d2049442b5a6058ff002db
Author: Robert Newson <rn...@apache.org>
Date:   2016-03-24T11:26:08Z

    Remove obsoleted R14-era code
    
    We no longer support R14 so we're dropping R14-specific complications
    in the codebase.
    
    COUCHDB-2975

commit eb93044ca4aa02ab4427ec7082df37bae6602973
Author: Robert Newson <rn...@apache.org>
Date:   2016-03-24T11:29:10Z

    Use transient restart type for all replications
    
    We want replication tasks to be restarted automatically if they crash
    abnormally. Replication tasks that complete or are cancelled (by
    deleting the backing _replicator doc or issuing an "cancel":true for
    non-persistent jobs) should still exit, should not be restarted, and
    should not have their child spec linger in the supervisor.
    
    COUCHDB-2975

commit 4cb517659c235c06a39ee7eb6b4150cdfded6116
Author: Robert Newson <rn...@apache.org>
Date:   2016-03-24T13:40:14Z

    Reduce likelihood of a bad replication job taking down the job supervisor
    
    While we can't disable max_restart_intensity, we can make it unlikely
    to happen. Ordinarily, we would want this behaviour, but replication
    jobs involve human input. A bad password, or malformed url, etc, can
    cause repeated and fast crashing.
    
    For now, we require ten crashes within one second before we would
    bounce the job supervisor. In future, we should manage replication
    jobs with greater care.
    
    COUCHDB-2975

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-couch-replicator pull request: restart replications on cra...

Posted by kxepal <gi...@git.apache.org>.
Github user kxepal commented on the pull request:

    https://github.com/apache/couchdb-couch-replicator/pull/33#issuecomment-200846727
  
    LGFM, +1. Good to see R14 bits away!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-couch-replicator pull request: restart replications on cra...

Posted by kxepal <gi...@git.apache.org>.
Github user kxepal commented on the pull request:

    https://github.com/apache/couchdb-couch-replicator/pull/33#issuecomment-200870682
  
    @rnewson Question? (sorry, I'm out of IRC). Well, it's hard to say for sure without giving a try to find the right values under different situations. I hope you did some research on this already and knows the best. I'm really not sure about this now, sorry ):


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-couch-replicator pull request: restart replications on cra...

Posted by rnewson <gi...@git.apache.org>.
Github user rnewson commented on the pull request:

    https://github.com/apache/couchdb-couch-replicator/pull/33#issuecomment-200867271
  
    @kxepal any thoughts on the restart intensity question?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-couch-replicator pull request: restart replications on cra...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/couchdb-couch-replicator/pull/33


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-couch-replicator pull request: restart replications on cra...

Posted by davisp <gi...@git.apache.org>.
Github user davisp commented on the pull request:

    https://github.com/apache/couchdb-couch-replicator/pull/33#issuecomment-200961456
  
    +1


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---