[SERVER-36476] Don't check index key size on the secondary Created: 06/Aug/18 Updated: 29/Oct/23 Resolved: 15/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Xiangyu Yao (Inactive) | Assignee: | Xiangyu Yao (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Storage NYC 2018-08-27 | ||||||||
| Participants: | |||||||||
| Description |
|
It's possible to have a scenario that while the secondary is building index at background, the FCV is set from 4.2 to 4.0. In that case,the index key size check should still be bypassed because long index keys already exist on the primary. Secondaries should unconditionally accept large index keys. |
| Comments |
| Comment by Githook User [ 15/Aug/18 ] |
|
Author: {'name': 'Xiangyu Yao', 'email': 'xiangyu.yao@mongodb.com', 'username': 'xy24'}Message: |
| Comment by Xiangyu Yao (Inactive) [ 13/Aug/18 ] |
|
Note that the work has been done in |