> On Jul 27, 2015, at 11:33 AM, Jan Lehnardt <j...@apache.org> wrote:
>
>>
>> On 27 Jul 2015, at 13:46, Jan Lehnardt <j...@apache.org> wrote:
>>
>>
>>> On 26 Jul 2015, at 19:03, Jan Lehnardt <j...@apache.org> wrote:
>>>
>>>
>>>> On 26 Jul 2015, at 14:47, Jan Lehnardt <j...@apache.org> wrote:
>>>>
>>>> Hey all,
>>>>
>>>> I’m trying to upgrade a database from 1.6.1 to 2.0.0/master/0c579b98 and
>>>> I’m seeing a number of issues.
>>>>
>>>> Any help is greatly appreciated. Since this is our official upgrade path
>>>> for 2.0, this has to be rock-solid.
>>>>
>>>> Feel free to break out individual issue into new threads, if it helps
>>>> keeping things organised.
>>>>
>>>> Scroll down for detailed information about the database, and machine
>>>> configurations.
>>>>
>>>>
>>>> ## The Scenario
>>>>
>>>> Replication is running on 2.0, pulling from 1.6.1 over the EC2 internal ip
>>>> address.
>>>>
>>>> ## The Issues
>>>>
>>>> 1. repeated log entries for “write quorum for <targetdb> failed”. I’ve
>>>> seen this in other contexts as well, why is this happening and should it?
>>>>
>>>>
>>>> 2. getting a lot of “cassim_metadata_cache changes listener died” from all
>>>> nodes about every 5 seconds. What’s up with these?
>>>>
>>>> - 2015-07-26 08:30:34.400 [error] Undefined emulator Error in process
>>>> <0.14633.26> on node 'node3@127.0.0.1' with exit value:
>>>> {function_clause,[{cassim_metadata_cache,changes_callback,[waiting_for_updates,"0"]},{fabric_view_changes,keep_sending_changes,8},{fabric_view_changes,go,5}]}
>>>>
>>>> - 2015-07-26 08:30:39.401 [notice] node3@127.0.0.1 <0.314.0>
>>>> cassim_metadata_cache changes listener died
>>>> {function_clause,[{cassim_metadata_cache,changes_callback,[waiting_for_updates,"0"]},{fabric_view_changes,keep_sending_changes,8},{fabric_view_changes,go,5}]}
>>>
>>> Alexander pointed to
>>> https://github.com/apache/couchdb-fabric/commit/b6659c8344c9a028b5ab451be41a991801c2ab3d#diff-2af86e058b4e7a4a99a7c5a12da6debdR96
>>> which is part of Adam’s recent work on COUCHDB-2724.
>>>
>>> Adam, any insights? :)
>>
>> Bob says this should fix it:
>> https://gist.github.com/rnewson/b9efd4f45e1c62315816
>>
>> In the meantime, I reverted the changes optimisation commit on fabric and
>> now I’m getting this once it is time to start replicating more documents
>> after the existing update sequence is all caught up with during replication:
>>
>> https://gist.github.com/janl/75804904dad73d17ed0e
>>
>> During which I found out that there *are* a few small attachments in the
>> source database, sorry for the confusion about this earlier.
>>
>> I still see function_clause errors after the revert, Bob suggests to wait
>> for Adam to comment.
>
> Bob’s latest commits fixed the replication issue, but I’d love to hear about
> the other things I mentioned.
>
> Best
> Jan
> —
Has there been any further OOB progress on the issues Jan enumerated here?
Adam
