Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.0.2, 1.0.3
    • Fix Version/s: None
    • Component/s: Replication
    • Environment:

      CentOS 5.6 64 bit, XFS HDD drive. Spidermonkey 1.9.2 or 1.7

      Description

      We have a setup replicating 7 databases from a master to slave. 2 databases use filters. One of these databases (the infrequently updated one) is failing replication. We have a cronjob to poll replication once per minute, and these stack traces appear often in the logs.

      The network is a gigabit lan, or 2 vms on the same host (same result seen on both).
      The replication job is called by sshing into the target and then curling the source database to localhost
      Source -> Target

      ssh TargetServer 'curl -sX POST -H "content-type:application/json" http://localhost:5984/_replicate -d

      {"source":"http://SourceServer:5984/DataBase","target":"DataBase","continuous":true,"filter":"productionfilter/notProcessingJob"}

      '

      changes_timeout is not defined in the ini files.

      Logs attached for stack traces on the source couch and the target couch

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              Alex Markham
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Development