couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filipe David Manana <fdman...@apache.org>
Subject Re: Replication hangs on streaming inline document attachments
Date Fri, 16 Jul 2010 21:51:46 GMT
On Fri, Jul 16, 2010 at 7:27 PM, Nikolai Teofilov <n.teofilov@gmail.com> wrote:
> Hi Filipe,
>
> Actually I swear my wife not to go online ;) in my vacation. I would love to test it
but it will be not possible for me in the next two weeks.

I understand, I do have the same kind of requests from mine all the time :)

>
> The first what I will do after the vacation is to test your patch.

Great. It's committed in trunk and branch 1.0.x.

>
> Best Regards from Sofia
> Nikolai

Best regards from Lisbon to Bulgaria then, and enjoy your holidays.

cheers

>
> Sent from my iPhone
>
> On Jul 16, 2010, at 13:02, Filipe David Manana <fdmanana@apache.org> wrote:
>
>> On Fri, Jul 16, 2010 at 5:41 AM, Nikolai Teofilov <n.teofilov@gmail.com> wrote:
>>> I am sorry but I was not able to create the ticket yesterday and today I am on
in vacantion ...
>>> No internet i next 15 days :(
>>
>> Hi Nikolai,
>> The ticket was created :)
>>
>> I think the solution in the meanwhile would be to upgrade your 0.11 to
>> 1.0 (or to 0.11.1 and do a push replication to 1.0). Another solution
>> would be for you to compile the branch 1.0.x (after the fix is
>> commited).
>>
>> cheers
>>
>>>
>>> Cheers
>>> Nikolai
>>>
>>>
>>> On 16.07.2010, at 02:03, Filipe David Manana wrote:
>>>
>>>> On Thu, Jul 15, 2010 at 10:52 PM, Nikolai Teofilov <n.teofilov@gmail.com>
wrote:
>>>>> Filipe,
>>>>>
>>>>> Yes, it happens only on replication from 0.11 (windows port) to 1.0.0
CouchDBX
>>>>> 1.0->1.0 no problem!
>>>>>
>>>>> Shell i create a ticket?
>>>>
>>>> Yes, please.
>>>> I was able to reproduce the problem. It happens when, from a CouchDB
>>>> 1.0 server, we do a pull replication with the source being a URL
>>>> pointing to a Couch 0.11 and the target is a local DB (1.0).
>>>>
>>>> I have a temporary solution now, but will add it later.
>>>>
>>>> cheers
>>>>
>>>>>
>>>>> cheers
>>>>> Nikolai
>>>>>
>>>>> On 15.07.2010, at 23:43, Filipe David Manana wrote:
>>>>>
>>>>>> So, it only happens on push replication, from a 0.11 Couch to a 1.0.0
Couch?
>>>>>>
>>>>>> I think I know where the issue is. Expect a fix soon (if I'm able
to
>>>>>> reproduce the issue).
>>>>>>
>>>>>> cheers
>>>>>>
>>>>>> On Thu, Jul 15, 2010 at 9:47 PM, Nikolai Teofilov <n.teofilov@gmail.com>
wrote:
>>>>>>>
>>>>>>> The problem apear to exist onliy on replication 0.11 to 1.0
>>>>>>>
>>>>>>> How to reproduce the bug:
>>>>>>>
>>>>>>> On couchdb 0.11 create a database with a document that contains
inline base64 encoded attachment.
>>>>>>>
>>>>>>>
>>>>>>> {
>>>>>>>  "_id" : "test",
>>>>>>>  "_attachments":
>>>>>>>  {
>>>>>>>    "foo.txt":
>>>>>>>    {
>>>>>>>      "content_type":"text\/plain",
>>>>>>>      "data": "VGhpcyBpcyBhIGJhc2U2NCBlbmNvZGVkIHRleHQ="
>>>>>>>    }
>>>>>>>  }
>>>>>>> }
>>>>>>>
>>>>>>> replication 0.11 -> (CouchDBX) 1.0 will hang with following
error log:
>>>>>>>
>>>>>>> 1> [info] [<0.1028.0>] starting new replication "5427f9ab10e93ee8b02bd9a3e0050c58"
at <0.1069.0>
>>>>>>> 1> [error] [<0.1083.0>] streaming att. ended but more
data requested {1279,225570,362980}
>>>>>>> 1> [info] [<0.1083.0>] request for "test/foo.txt" timed
out, retrying in 0.5 seconds
>>>>>>> 1> [error] [<0.1083.0>] streaming att. ended but more
data requested {1279,225571,40192}
>>>>>>> 1> [info] [<0.1083.0>] request for "test/foo.txt" timed
out, retrying in 0.5 seconds
>>>>>>> 1> [error] [<0.1083.0>] streaming att. ended but more
data requested {1279,225574,323477}
>>>>>>> 1> [info] [<0.1083.0>] request for "test/foo.txt" timed
out, retrying in 0.5 seconds
>>>>>>> 1> [error] [<0.1083.0>] streaming att. ended but more
data requested {1279,225575,24131}
>>>>>>> 1> [info] [<0.1083.0>] request for "test/foo.txt" timed
out, retrying in 0.5 seconds
>>>>>>> 1> [error] [<0.1083.0>] streaming att. ended but more
data requested {1279,225575,688384}
>>>>>>> 1> [info] [<0.1083.0>] request for "test/foo.txt" timed
out, retrying in 0.5 seconds
>>>>>>> 1> [error] [<0.1083.0>] streaming att. ended but more
data requested {1279,225576,382178}
>>>>>>> 1> [info] [<0.1083.0>] request for "test/foo.txt" timed
out, retrying in 0.5 seconds
>>>>>>>
>>>>>>> Cheers
>>>>>>> Nikolai
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Filipe David Manana,
>>>>>> fdmanana@apache.org
>>>>>>
>>>>>> "Reasonable men adapt themselves to the world.
>>>>>>  Unreasonable men adapt the world to themselves.
>>>>>>  That's why all progress depends on unreasonable men."
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Filipe David Manana,
>>>> fdmanana@apache.org
>>>>
>>>> "Reasonable men adapt themselves to the world.
>>>>  Unreasonable men adapt the world to themselves.
>>>>  That's why all progress depends on unreasonable men."
>>>
>>>
>>
>>
>>
>> --
>> Filipe David Manana,
>> fdmanana@apache.org
>>
>> "Reasonable men adapt themselves to the world.
>>  Unreasonable men adapt the world to themselves.
>>  That's why all progress depends on unreasonable men."
>



-- 
Filipe David Manana,
fdmanana@apache.org

"Reasonable men adapt themselves to the world.
 Unreasonable men adapt the world to themselves.
 That's why all progress depends on unreasonable men."

Mime
View raw message