CouchDB
  1. CouchDB
  2. COUCHDB-596

Replication tasks sometimes never complete

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 0.11
    • Fix Version/s: None
    • Component/s: Database Core
    • Labels:
      None
    • Skill Level:
      Committers Level (Medium to Hard)

      Description

      In my recent testing with trunk, I kick off around 10 replication tasks in quick succession, each for databases with at least a few thousand documents. More often than not, one or two of these replication tasks never completes; the response is never returned to the calling thread and the tasks remain present in _active_tasks until the server is rebooted.

        Issue Links

          Activity

          Hide
          Randall Leeds added a comment -

          Per Adam's comment, possibly related to 597. I'm marking this as such so that when 597 is fixed we'll be reminded to check for repro and maybe close this.

          Show
          Randall Leeds added a comment - Per Adam's comment, possibly related to 597. I'm marking this as such so that when 597 is fixed we'll be reminded to check for repro and maybe close this.
          Randall Leeds made changes -
          Link This issue relates to COUCHDB-597 [ COUCHDB-597 ]
          Paul Joseph Davis made changes -
          Skill Level Committers Level (Medium to Hard)
          Filipe Manana made changes -
          Field Original Value New Value
          Link This issue relates to COUCHDB-793 [ COUCHDB-793 ]
          Hide
          Adam Kocoloski added a comment -

          It's possible that the issues I described in COUCHDB-597 could cause this too, if the changes feed had been fully downloaded. That's the only timeout we have; everyone else is content to wait forever while the attachment receiver is stuck waiting for a message that will never come.

          Show
          Adam Kocoloski added a comment - It's possible that the issues I described in COUCHDB-597 could cause this too, if the changes feed had been fully downloaded. That's the only timeout we have; everyone else is content to wait forever while the attachment receiver is stuck waiting for a message that will never come.
          Robert Newson created issue -

            People

            • Assignee:
              Unassigned
              Reporter:
              Robert Newson
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Development