On Fri, Jul 25, 2014 at 5:29 AM, Stuart Bishop
wrote:
> On 25 July 2014 12:05, Gustavo Niemeyer
> wrote:
> The bug Ian cites and is trying to work around has sessions failing
> with an i/o error after some time (I'm guessing resource starvation in
> MongoDB or TCP networking issues). session.Cop
On 25 July 2014 12:05, Gustavo Niemeyer wrote:
> On Fri, Jul 25, 2014 at 1:02 AM, Ian Booth wrote:
>> We've transitioned to using Session.Copy() to address the situation whereby
>> Juju
>> would create a mongo collection instance and then continue to make db calls
>> against that collection with
On Fri, Jul 25, 2014 at 2:37 AM, Ian Booth wrote:
> The tests passed for me every time also, with and without independent
> sessions.
> If I loaded my machine to max out CPU usage to 100%, then the tests (different
> ones each run) would fail intermittently but reproducibly every time with
> sess
>
> That said, the goal is of course not to make the developer's life
> miserable. All the driver wants is an acknowledgement that the error
> was perceived and taken care of. This is done trivially by calling:
>
> session.Refresh()
>
So in Juju now, we use session.Copy() which calls Refresh
On Fri, Jul 25, 2014 at 1:02 AM, Ian Booth wrote:
> We've transitioned to using Session.Copy() to address the situation whereby
> Juju
> would create a mongo collection instance and then continue to make db calls
> against that collection without realising the underlying socket may have
> become
On 25/07/14 03:26, Gustavo Niemeyer wrote:
> Hey Ian,
>
> On Thu, Jul 24, 2014 at 4:03 AM, Ian Booth wrote:
>> However, doing a session.Copy() each time the transaction log collection is
>> queried (every 5 seconds) causes a number of test failures when the host
>> machine
>> is heavily loaded
Hey Ian,
On Thu, Jul 24, 2014 at 4:03 AM, Ian Booth wrote:
> However, doing a session.Copy() each time the transaction log collection is
> queried (every 5 seconds) causes a number of test failures when the host
> machine
> is heavily loaded. Either extra events are received or events are missed
So, we have some intermittently failing tests in state/watcher.
The tests fail when the machine on which they are run is heavily loaded.
The watcher infrastructure essentially polls every 5 seconds the txns.log
collection to see what new transactions have been written and turns any new
transaction
