[SERVER-32537] Potential use of an uninitialized UUID value during chunk migration Created: 03/Jan/18 Updated: 04/Jan/18 Resolved: 04/Jan/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.6.1, 3.7.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
The chunk migration startup code can potentially return a default-constructed UUID value, which will later on be used to notify the shard secondary. Because of this, for collections which do not have UUIDs, we will write some garbage UUID value, which can be misinterpreted. |
| Comments |
| Comment by Ramon Fernandez Marina [ 04/Jan/18 ] |
|
This will be taken care of by |