[COMPASS-4064] Incorrect Index creation status Created: 30/Dec/19 Updated: 12/Aug/20 Resolved: 12/Aug/20 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Background Operations, Indexes |
| Affects Version/s: | None |
| Fix Version/s: | No version |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Manivannan Ponnusamy | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Documentation Changes: | Not Needed |
| Sprint: | Iteration Xerus, Iteration Yak, Iteration Zebra, Iteration Avocado, Iteration Blackberry, Iteration Cantaloupe, Iteration Dragon Fruit, Iteration Elderberry, Iteration Fig, Iteration Guanábana, Iteration Huckleberry, Iteration Icaco, Iteration Jackfruit |
| Description |
|
Hi, I have a collection with close 2.1 billion documents in it. I was trying to create an index from the compass index tab, it started creating the index but after seconds it got errored out saying it's not able to access the collection. But the index was getting created from the backend. I was able to see it from CurrentOP command. Also, it didn't create index in all the 8 shards. In some shards, the indexes were not created. I need to manually log into each shard and check the status. But from the compass index tab, it shows created but it's not.
Note: Installation Type - Sharded cluster with 8 shards. |
| Comments |
| Comment by Massimiliano Marcon [ 12/Aug/20 ] |
|
Closing this since we have not heard back from submitter for a few months. Assuming this is due to how Compass handles (or does not handle) background operations. We will tackle it with a project in the future. |