[SERVER-14607] Some index intersection plans return internal data instead of the correct result set. Created: 18/Jul/14 Updated: 11/Mar/15 Resolved: 24/Jul/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 2.6.3 |
| Fix Version/s: | 2.6.4, 2.7.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tomas Kulich | Assignee: | David Storch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Backport Completed: | |||||||||
| Steps To Reproduce: | To examine: 1. ssh ubuntu@54.77.0.143 (pw: #######)
Each document in the output should look like {"":1234}which is clearly wrong. Restart mongodb service to see the proper output. additional notes:
|
||||||||
| Participants: | |||||||||
| Description |
| Comments |
| Comment by Githook User [ 24/Jul/14 ] | ||||
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: | ||||
| Comment by Githook User [ 24/Jul/14 ] | ||||
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: (cherry picked from commit 7acc48b74c6c0755e63a0358521055aae9792cd4) | ||||
| Comment by Githook User [ 24/Jul/14 ] | ||||
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: | ||||
| Comment by Tomas Kulich [ 19/Jul/14 ] | ||||
|
Oh, it's good that you can create/restore dump while preserving the invalid state. For me, the DB gets repaired once I dumped/restored it. This was the reason, why I reported the bug this way Anyways, great that you can reproduce it, I'm shutting down the AWS instance. | ||||
| Comment by J Rassi [ 18/Jul/14 ] | ||||
|
Uploaded "dump.tgz", a dump of the collection created by the provided script. To reproduce, restore the dump into a 2.6.3 instance and run the following:
tomas.kulich@gmail.com: thanks for setting up the live instance for us to examine. We're able to reproduce the issue ourselves, so feel free to take the instance down. | ||||
| Comment by Tomas Kulich [ 18/Jul/14 ] | ||||
|
That's great! Thank you! | ||||
| Comment by hari.khalsa@10gen.com [ 18/Jul/14 ] | ||||
|
Thanks for reporting this, tomas.kulich@gmail.com. We've identified the underlying issue and will have a fix very shortly. It will be included in the next release of 2.6. | ||||
| Comment by Thomas Rueckstiess [ 18/Jul/14 ] | ||||
|
Hi Tomas, Thanks for reporting this, and for providing a demo instance to illustrate the behavior. We will look into it and get back to you when we know more. Regards, | ||||
| Comment by Tomas Kulich [ 18/Jul/14 ] | ||||
|
one more thing - I never get this bug on mongo v. 2.4 |