Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.1.1
    • Fix Version/s: 1.2, 1.2.1
    • Component/s: Replication
    • Labels:
    • Environment:

      Description

      It seems our replication has stopped, reporting an error
      [emulator] Error in process <0.21599.306> nocatch,{invalid_json,<<0 bytes>>,[

      {couch_util,json_decode,1}

      ,

      {couch_rep_reader,'-open_doc_revs/3-lc$^1/1-1-',1},{couch_rep_reader,'-open_doc_revs/3-lc$^1/1-1-',1}

      ,

      {couch_rep_reader,open_doc_revs,3}

      ,{couch_rep_reader,'spawn_document_request/4-fun-0'...

      It was all working until we upgraded some other couches in our replication "web" from couch 1.0.3 to couch 1.1.1. We then set of database and view compactions, and sometime overnight some of the replication links stopped.

      I have curled the command myself, both as a multipart message and a single json response (with header "Accept:application/json" ) and it can be parsed correctly by Python simplejson - I have attached it here aswell - called "troublecurl-redacted.txt" - though it is 18.8mb. The request takes about 6 seconds.

      I don't quite understand why it is reported as invalid JSON? Other reports similar to this that I googled mentioned blank document ids, but I can't see any of these.

        Attachments

        1. old_rep_qs_encoding.patch
          2 kB
          Filipe Manana
        2. 9c94ed0e23508f4ec3d18f8949c06a5b replicaton from wireshark cut.txt
          324 kB
          Alex Markham
        3. replication error wireshark.txt
          8 kB
          Alex Markham
        4. source couch error.log
          7 kB
          Alex Markham
        5. target couch error.log
          23 kB
          Alex Markham

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: