[SERVER-17840] MONGOS 3.0.1 LOG bypassing setShardVersion Created: 01/Apr/15 Updated: 15/May/15 Resolved: 15/May/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Sharding |
| Affects Version/s: | 3.0.1 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Dmitry | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Hello. What's mean in mongos log
for all rs nodes once in 5 minutes ffter upgrading 2.6.8 to 3.0.1 ? In one rs I see in log connections from another rs, such as:
Looks like not OK. |
| Comments |
| Comment by Ramon Fernandez Marina [ 15/May/15 ] |
|
esp1974, since the SERVER project is for reporting bugs or feature suggestions for the MongoDB server I'm going to resolve this issue. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like your last one involving more discussion would be best posted on the mongodb-user group. Regards, |
| Comment by Dmitry [ 01/Apr/15 ] |
|
Hello Randolph. WBW, |
| Comment by Randolph Tan [ 01/Apr/15 ] |
|
It means that the primary was temporarily unavailable and mongos decided to skip the shard version handshake (since it can't with no primary) and proceed to talk with the secondary (this is only possible if the query/command has the right read preference). This means that reads can potentially be stale depending on how up to date the secondaries are. |