On Sunday, September 23, 2012 6:50:21 AM UTC-4, tetlika wrote:
> Jessem looks it was fixed after we've implemented the fix you've suggested
> thanks!
> Середа, 12 вересня 2012 р. 22:01:46 UTC+3 користувач A. Jesse Jiryu Davis
> написав:
>> Michael, tetlika, are you still experiencing this issue? Have you updated
>> your code to use a single Connection, persisting for the lifetime of the
>> process, for all operations?
>> On Friday, September 7, 2012 11:10:40 AM UTC-4, A. Jesse Jiryu Davis
>> wrote:
>>> You should create a single Connection instance used by all operations in
>>> all threads for the lifetime of the application process. This will maximize
>>> performance, minimize the total number of open sockets, and minimize the
>>> time required to recover from an event like a database server shutting
>>> down. This last point is a little subtle -- a Connection doesn't know that
>>> a database server went down until it tries an operation. Then it raises an
>>> AutoReconnect exception, and on the next operation, it resets the
>>> connection, connecting to the correct server. So if you have 10 distinct
>>> Connection instances, they each must fail, raise an AutoReconnect, and
>>> reset. If you have one Connection, you need go through this process only
>>> once.
>>> On Friday, September 7, 2012 6:01:34 AM UTC-4, Michael Korbakov wrote:
>>>> Hi Jesse! Thank you for helping us.
>>>> I'm working with tetlika and can answer your question. We're using
>>>> Mongokit-0.7.2 and create one Connection instance per document model. That
>>>> was done quite a long time ago to workaround connection pooling issues. I
>>>> think we can change these multiple connection instances to single DB
>>>> connection quite easy. Do you think that it could be root of the problem
>>>> we're facing?
>>>> четверг, 6 сентября 2012 г., 23:32:42 UTC+3 пользователь A. Jesse Jiryu
>>>> Davis написал:
>>>>> Do you create a single Connection instance for the lifetime of the
>>>>> application, or more frequently than that? Can you provide a complete test
>>>>> script please?
>>>>> On Thursday, September 6, 2012 4:00:11 PM UTC-4, tetlika wrote:
>>>>>> very weird, before submitting I've reproduced it 4 times: once we
>>>>>> faced that on production, and 3 times in staging envirinment
>>>>>> mongod is 2.0.6
>>>>>> could you please try with the exact same connection:
>>>>>> mongokit.connection.Connection(settings.MONGODB[db_id]
>>>>>> ['master'][0],settings.MONGODB[db_id]['master'][1])
>>>>>> On 6 Вер, 22:54, "A. Jesse Jiryu Davis" <je...@10gen.com> wrote:
>>>>>> > I can't reproduce your issue. In EC2 I set up two instances, one
>>>>>> with a
>>>>>> > mongod which I forced to be primary, and one with a secondary and
>>>>>> an
>>>>>> > arbiter. With PyMongo 2.1.1:
>>>>>> > >>> c = Connection(['
>>>>>> ec2-176-34-219-188.eu-west-1.compute.amazonaws.com',
>>>>>> > 'ec2-54-247-137-15.eu-west-1.compute.amazonaws.com'])>>> c.host #
>>>>>> Which instance has the primary right now?
>>>>>> > u'ec2-54-247-137-15.eu-west-1.compute.amazonaws.com'
>>>>>> > >>> c.test.test.find_one()
>>>>>> > {u'_id': ObjectId('5048f365923450f553000000')}
>>>>>> > >>> # In AWS console, I stop the instance with the primary. The
>>>>>> instance
>>>>>> > with secondary
>>>>>> > >>> # and arbiter is still up, so secondary becomes new primary.
>>>>>> > >>> c.test.test.find_one() # Expect first try to fail
>>>>>> > Traceback (most recent call last)
>>>>>> > pymongo/collection.py in find_one(self, spec_or_id, *args,
>>>>>> **kwargs)
>>>>>> > pymongo/cursor.py in next(self)
>>>>>> > pymongo/cursor.py in _refresh(self)
>>>>>> > pymongo/cursor.py in __send_message(self, message)
>>>>>> > pymongo/connection.py in _send_message_with_response(self,
>>>>>> message,
>>>>>> > _must_use_master, **kwargs)
>>>>>> > pymongo/connection.py in __socket(self)
>>>>>> > pymongo/connection.py in get_socket(self, host, port)
>>>>>> > pymongo/connection.py in connect(self, host, port)
>>>>>> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/sock
>>>>>> et.pyc
>>>>>> > in meth(name, self, *args)
>>>>>> > timeout: timed out
>>>>>> > >>> c.test.test.find_one() # Second try works as expected
>>>>>> > {u'_id': ObjectId('5048f365923450f553000000')}
>>>>>> > >>> c.host # New primary's instance
>>>>>> > u'ec2-176-34-219-188.eu-west-1.compute.amazonaws.com'
>>>>>> > After PyMongo throws a timeout error, it reconnects and detects the
>>>>>> new
>>>>>> > primary during the next operation. So we expect only one timeout
>>>>>> after you
>>>>>> > stop an instance in EC2.
>>>>>> > On Thursday, September 6, 2012 2:33:35 PM UTC-4, tetlika wrote:
>>>>>> > > on ec2
>>>>>> > > On 6 Вер, 21:33, "A. Jesse Jiryu Davis" <je...@10gen.com> wrote:
>>>>>> > > > OK, I need to test a theory; stay tuned. Are your machines in
>>>>>> EC2 or
>>>>>> > > your
>>>>>> > > > own data center or what?
>>>>>> > > > On Thursday, September 6, 2012 2:27:52 PM UTC-4, tetlika wrote:
>>>>>> > > > > single
>>>>>> > > > > On 6 Вер, 21:26, "A. Jesse Jiryu Davis" <je...@10gen.com>
>>>>>> wrote:
>>>>>> > > > > > I might understand the problem. Is your application
>>>>>> single-threaded
>>>>>> > > or
>>>>>> > > > > > multi-threaded?
>>>>>> > > > > > On Thursday, September 6, 2012 2:18:05 PM UTC-4, tetlika
>>>>>> wrote:
>>>>>> > > > > > > yes, that's correct
>>>>>> > > > > > > On 6 Вер, 21:16, "A. Jesse Jiryu Davis" <je...@10gen.com>
>>>>>> wrote:
>>>>>> > > > > > > > OK, thanks. So your code is equivalent to this?:
>>>>>> > > > > > > > mongokit.connection.Connection(['
>>>>>> replaqueue.internal.com',
>>>>>> > > > > > > > 'replbqueue.internal.com'], 27017)
>>>>>> > > > > > > > On Thursday, September 6, 2012 2:05:28 PM UTC-4, A.
>>>>>> Jesse Jiryu
>>>>>> > > > > Davis
>>>>>> > > > > > > wrote:
>>>>>> > > > > > > > > Thanks, and what are the values of
>>>>>> > > > > > > settings.MONGODB[db_id]['master'][0]and
>>>>>> > > > > > > > > settings.MONGODB[db_id]['master'][1]? Are you
>>>>>> configuring any
>>>>>> > > > > timeouts
>>>>>> > > > > > > in
>>>>>> > > > > > > > > PyMongo or MongoKit, or using the default timeouts?
>>>>>> > > > > > > > > On Thursday, September 6, 2012 1:55:20 PM UTC-4,
>>>>>> tetlika
>>>>>> > > wrote:
>>>>>> > > > > > > > >> sorry, previous was a bit wrongly formatted
>>>>>> > > сonnection=mongokit.connection.Connection(settings.MONGODB[db_id]
>>>>>> > > > > > > > >> ['master'][0],settings.MONGODB[db_id]['master'][1])
>>>>>> > > > > > > > >> while ['master'][0] are ['master'][1] defined in
>>>>>> config as
>>>>>> > > > > slave
>>>>>> > > > > > > and
>>>>>> > > > > > > > >> master hosts of replica
>>>>>> > > > > > > > >> On 6 Вер, 20:51, tetlika <tetl...@gmail.com> wrote:
>>>>>> > > > > > > > >> > connection =
>>>>>> > > > > > > mongokit.connection.Connection(settings.MONGODB[db_id]
>>>>>> > > > > > > > >> > ['master'][0],
>>>>>> > > > > > > settings.MONGODB[db_id]
>>>>>> > > > > > > > >> > ['master'][1])
>>>>>> > > > > > > > >> > On 6 Вер, 20:49, tetlika <tetl...@gmail.com>
>>>>>> wrote:
>>>>>> > > > > > > > >> > > centOS 5.6 x64 everywhere
>>>>>> > > > > > > > >> > > python 2.7.3
>>>>>> > > > > > > > >> > > wait a bit - I will provide the code , I hope
>>>>>> > > > > > > > >> > > On 6 Вер, 20:42, "A. Jesse Jiryu Davis" <
>>>>>> je...@10gen.com>
>>>>>> > > > > wrote:
>>>>>> > > > > > > > >> > > > What operating system are you using on the
>>>>>> client
>>>>>> > > (where
>>>>>> > > > > Python
>>>>>> > > > > > > > >> runs) and
>>>>>> > > > > > > > >> > > > on the MongoDB servers? What Python version?
>>>>>> Can you
>>>>>> > > > > provide
>>>>>> > > > > > > the
>>>>>> > > > > > > > >> exact code
>>>>>> > > > > > > > >> > > > you use to create the PyMongo
>>>>>> ReplicaSetConnection? I
>>>>>> > > need
>>>>>> > > > > to
>>>>>> > > > > > > see
>>>>>> > > > > > > > >> precisely
>>>>>> > > > > > > > >> > > > what options you pass to ReplicaSetConnection.
>>>>>> > > > > > > > >> > > > Thanks.
>>>>>> > > > > > > > >> > > > On Wednesday, September 5, 2012 12:14:33 PM
>>>>>> UTC-4,
>>>>>> > > tetlika
>>>>>> > > > > > > wrote:
>>>>>> > > > > > > > >> > > > > can anyone help me on that?
>>>>>> > > > > > > > >> > > > > On 5 Вер, 18:08, tetlika <tetl...@gmail.com>
>>>>>> wrote:
>>>>>> > > > > > > > >> > > > > > in second scenario of course the fail over
>>>>>> is not
>>>>>> > > > > happening
>>>>>> > > > > > > > >> > > > > > immediately, - it takes 10-15 seconds or
>>>>>> so
>>>>>> > > > > > > > >> > > > > > but in scenario 1 - the fail over is not
>>>>>> happening
>>>>>> > > at
>>>>>> > > > > least
>>>>>> > > > > > > for
>>>>>> > > > > > > > >> 30-40
>>>>>> > > > > > > > >> > > > > > minutes
>>>>>> > > > > > > > >> > > > > > On 5 Вер, 18:05, Stephan <
>>>>>> sboeseb...@googlemail.com>
>>>>>> > > > > > > wrote:
>>>>>> > > > > > > > >> > > > > > > Actually, in Java I always see the first
...
