[SERVER-13606] SyncClusterConnection should not rely on the 'locktype' field in the help command Created: 16/Apr/14 Updated: 13/Jul/15 Resolved: 13/Jul/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Currently, SyncClusterConnection invokes help on the config servers for each command, which it receives in order to determine whether it is a write (has to be sent to 3 servers) or read command. This happens in SyncClusterConnection::_lockType. Instead of doing this, we should just have a fixed map in SyncClusterConnection, which specifies what is the type of a command. |
| Comments |
| Comment by Andy Schwerin [ 13/Jul/15 ] |
|
SCC won't be used by config-server replica sets, so we'll let this behavior stick around until sync-cluster config servers no longer exist. |