[SERVER-27531] setFeatureCompatibilityVersion to 3.4 Created: 28/Dec/16 Updated: 18/Jan/17 Resolved: 18/Jan/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 3.4.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | yang hao | Assignee: | Kelsey Schubert |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
when we setFeatureCompatibilityVersion to 3.4 , name: "incompatible_with_version_32", ns: "admin.system.version" } |
| Comments |
| Comment by Kelsey Schubert [ 18/Jan/17 ] | ||||||||
|
Hi 282848081@qq.com, We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket. Regards, | ||||||||
| Comment by Tess Avitabile (Inactive) [ 05/Jan/17 ] | ||||||||
|
I can confirm by looking at the logs that the shard received the command {setFeatureCompatibilityVersion: "3.4"}:
The command succeeded:
Immediately after, the shard received the command {setFeatureCompatibilityVersion: "3.2"}:
This command also succeeded:
I do not know why the shard received the command {setFeatureCompatibilityVersion: "3.2"}. It would be helpful to see logs from the mongos and/or the config primary. If running the command {setFeatureCompatibilityVersion: "3.4"} on the mongos returned an error message, that would be useful too. Thank you for your help! | ||||||||
| Comment by Tess Avitabile (Inactive) [ 04/Jan/17 ] | ||||||||
|
Thank you, the logs from the shard primary are very helpful. Can you also please attach the log of the mongos? | ||||||||
| Comment by yang hao [ 30/Dec/16 ] | ||||||||
|
log file is conn151 | ||||||||
| Comment by Daniel Pasette (Inactive) [ 29/Dec/16 ] | ||||||||
|
can you attach the complete log of the mongos which you ran the setFeatureCompatibility command on as well as the complete log of one of the primary nodes of one of you shard replica sets? | ||||||||
| Comment by yang hao [ 29/Dec/16 ] | ||||||||
|
| ||||||||
| Comment by yang hao [ 29/Dec/16 ] | ||||||||
|
Hi Thomas, we upgrade from 3.2.10 we stop balance and upgrade the cluster use opsmanager(3.4.0.383) then start balance we execute it on mongos , fail, then use opsmanager set to 3.4 also fail. yes, all nodes in my cluster affected by this issue | ||||||||
| Comment by Kelsey Schubert [ 28/Dec/16 ] | ||||||||
|
Hi 282848081@qq.com, Thank you for reporting this issue. I have a few questions that will help us better understand what is happening.
Thanks for your help, |