[SERVER-10206] sharding/read_pref.js timed out on Nightly Linux 64-bit Subscription RHEL 6.2 Created: 15/Jul/13 Updated: 11/Jul/16 Resolved: 15/Nov/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matt Kangas | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | buildbot | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
buildbot-special Nightly Linux 64-bit Subscription RHEL 6.2 Build #504 |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
Nightly Linux 64-bit Subscription RHEL 6.2 Build #504 July 14 (rev dbc297ef013) http://buildbot-special.10gen.com/builders/Nightly%20Linux%2064-bit%20Subscription%20RHEL%206.2/builds/504/steps/shell_3/logs/stdio stdio ends with
|
| Comments |
| Comment by Randolph Tan [ 15/Nov/13 ] | |||||||||||||||||||||||||||||||||||
|
milkie thinks that the last failure was caused by our build logger being too slow to respond. This caused the replica sets to hang up while waiting for the logs to be flushed, which resulted in missing the heartbeats. | |||||||||||||||||||||||||||||||||||
| Comment by Randolph Tan [ 15/Nov/13 ] | |||||||||||||||||||||||||||||||||||
|
Test bailed out even before the setup finishes. It fails when it was about to add users inside ReplSetTest#initiate:
So, it gets the master connection, but for some reason, the nodes suddenly thinks the others are down, causing the current primary to step down:
As a consequence, causing the shell to lose connection and throw an exception when it tries to use the master connection to add user:
| |||||||||||||||||||||||||||||||||||
| Comment by Daniel Pasette (Inactive) [ 15/Nov/13 ] | |||||||||||||||||||||||||||||||||||
| Comment by Randolph Tan [ 04/Sep/13 ] | |||||||||||||||||||||||||||||||||||
|
Test timed out because one the servers died unexpectedly:
| |||||||||||||||||||||||||||||||||||
| Comment by Matt Kangas [ 04/Sep/13 ] | |||||||||||||||||||||||||||||||||||
|
Today this test failed on Windows 64-bit. It timed out internally, rather than hanging until buildbot killed it. Builder Windows 64-bit Build #5680 Wed Sep 4 (rev 805c07c3bb)
| |||||||||||||||||||||||||||||||||||
| Comment by Matt Kangas [ 22/Aug/13 ] | |||||||||||||||||||||||||||||||||||
|
Status: waiting for it to happen again after increasing the verbosity of the test | |||||||||||||||||||||||||||||||||||
| Comment by auto [ 24/Jul/13 ] | |||||||||||||||||||||||||||||||||||
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: Increase verbosity for | |||||||||||||||||||||||||||||||||||
| Comment by Matt Kangas [ 17/Jul/13 ] | |||||||||||||||||||||||||||||||||||
|
Now on Ubuntu: Nightly Linux 64-bit Subscription Ubuntu 1204 Build #172 July 17 http://buildbot-special.10gen.com/builders/Nightly%20Linux%2064-bit%20Subscription%20Ubuntu%201204/builds/172/steps/shell_3/logs/stdio
| |||||||||||||||||||||||||||||||||||
| Comment by Matt Kangas [ 17/Jul/13 ] | |||||||||||||||||||||||||||||||||||
|
renctan - ask Spencer, but I have seen this in the output from many different tests, and I believe it means the user credentials haven't been replicated to a secondary yet. | |||||||||||||||||||||||||||||||||||
| Comment by Randolph Tan [ 17/Jul/13 ] | |||||||||||||||||||||||||||||||||||
|
Not sure if this is relevant but this lines in the logs looks suspicious (appears in both logs):
Tried running the same test on the local machine with CRAM-MD5 and never saw this error. However, successful build in buildbot has this error... | |||||||||||||||||||||||||||||||||||
| Comment by Matt Kangas [ 15/Jul/13 ] | |||||||||||||||||||||||||||||||||||
|
Same thing, same night on a different builder: Nightly Linux 64-bit Subscription Amazon AMI Build #579 July 14 (rev dbc297ef0) http://buildbot-special.10gen.com/builders/Nightly%20Linux%2064-bit%20Subscription%20Amazon%20AMI/builds/579/steps/shell_3/logs/stdio stdio ends with
|