CouchDB
  1. CouchDB
  2. COUCHDB-690

replication fail -- couchdb crashed

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Cannot Reproduce
    • Affects Version/s: 0.10.1
    • Fix Version/s: None
    • Component/s: Replication
    • Environment:

      linux 2.6.30.7 - debian 5.0

    • Skill Level:
      Regular Contributors Level (Easy to Medium)

      Description

      We have a database on host A with 8.5 millions document. The size of the database is ~450GO.

      We first tried to start a continuous replication on a second host B. The replication stoped after only 1Go have been copied, and the replication never started again.

      We then copied the database file from host A on host B. When the file was copied, we started a replication from A to B, then the couchdb on host B crashed. It tooks a long time to fetch a list of IDs, then it appears in the logfile that a time out occured on host B, and immediatly after the couchdb instance on host B crashed.

      1. couch.log
        1.02 MB
        linkfluence

        Activity

        linkfluence created issue -
        linkfluence made changes -
        Field Original Value New Value
        Attachment couch.log [ 12438606 ]
        linkfluence made changes -
        Description We have a database on host A with 8.5 millions document. The size of the database is ~450GO.

        We first tried to start a continuous replication on a second host B. The replication stoped after only 1Go have been copied, and the replication never started again.

        We then copied the database file from host A on host B. When the file was copied, we started a replication from A to B, then the couchdb on host B crashed. It tooks a long time to fetch a list of IDs, then it appears in the logfile that a time out occured on host B, and immediatly after the couchdb instance on host B crashed.

        log file : http://overmind.rtgi.eu/couch.tgz
        We have a database on host A with 8.5 millions document. The size of the database is ~450GO.

        We first tried to start a continuous replication on a second host B. The replication stoped after only 1Go have been copied, and the replication never started again.

        We then copied the database file from host A on host B. When the file was copied, we started a replication from A to B, then the couchdb on host B crashed. It tooks a long time to fetch a list of IDs, then it appears in the logfile that a time out occured on host B, and immediatly after the couchdb instance on host B crashed.

        Paul Joseph Davis made changes -
        Skill Level Regular Contributors Level (Easy to Medium)
        Paul Joseph Davis made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Cannot Reproduce [ 5 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            linkfluence
          • Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development