Otherwise, you get this in your non-sharded log every time you step down:
[js_test:linearizable_read_concern] 2016-09-14T09:28:48.885-0400 d20013| 2016-09-14T09:28:48.884-0400 I SHARDING [conn2] Marking collection as not sharded. [js_test:linearizable_read_concern] 2016-09-14T09:28:48.885-0400 d20013| 2016-09-14T09:28:48.884-0400 I - [conn1] end connection 127.0.0.1:40044 (7 connections now open) [js_test:linearizable_read_concern] 2016-09-14T09:28:48.886-0400 d20013| 2016-09-14T09:28:48.884-0400 I SHARDING [conn2] Marking collection as not sharded. [js_test:linearizable_read_concern] 2016-09-14T09:28:48.886-0400 d20013| 2016-09-14T09:28:48.884-0400 I SHARDING [conn2] Marking collection as not sharded. [js_test:linearizable_read_concern] 2016-09-14T09:28:48.886-0400 d20013| 2016-09-14T09:28:48.884-0400 I SHARDING [conn2] Marking collection as not sharded. [js_test:linearizable_read_concern] 2016-09-14T09:28:48.886-0400 d20013| 2016-09-14T09:28:48.884-0400 I SHARDING [conn2] Marking collection as not sharded. [js_test:linearizable_read_concern] 2016-09-14T09:28:48.886-0400 d20013| 2016-09-14T09:28:48.884-0400 I SHARDING [conn2] Marking collection as not sharded. [js_test:linearizable_read_concern] 2016-09-14T09:28:48.886-0400 d20013| 2016-09-14T09:28:48.884-0400 I SHARDING [conn2] Marking collection as not sharded. [js_test:linearizable_read_concern] 2016-09-14T09:28:48.886-0400 d20013| 2016-09-14T09:28:48.884-0400 I SHARDING [conn2] Marking collection as not sharded. [js_test:linearizable_read_concern] 2016-09-14T09:28:48.886-0400 d20013| 2016-09-14T09:28:48.884-0400 I SHARDING [conn2] Marking collection as not sharded.
And every time you step up too!
[js_test:linearizable_read_concern] 2016-09-14T09:28:17.412-0400 d20013| 2016-09-14T09:28:17.411-0400 I SHARDING [rsSync] Marking collection as not sharded. [js_test:linearizable_read_concern] 2016-09-14T09:28:17.412-0400 d20013| 2016-09-14T09:28:17.411-0400 I SHARDING [rsSync] Marking collection as not sharded. [js_test:linearizable_read_concern] 2016-09-14T09:28:17.412-0400 d20013| 2016-09-14T09:28:17.411-0400 I SHARDING [rsSync] Marking collection as not sharded. [js_test:linearizable_read_concern] 2016-09-14T09:28:17.412-0400 d20013| 2016-09-14T09:28:17.411-0400 I SHARDING [rsSync] Marking collection as not sharded. [js_test:linearizable_read_concern] 2016-09-14T09:28:17.412-0400 d20013| 2016-09-14T09:28:17.411-0400 I SHARDING [rsSync] Marking collection as not sharded. [js_test:linearizable_read_concern] 2016-09-14T09:28:17.412-0400 d20013| 2016-09-14T09:28:17.411-0400 I SHARDING [rsSync] Marking collection as not sharded. [js_test:linearizable_read_concern] 2016-09-14T09:28:17.412-0400 d20013| 2016-09-14T09:28:17.411-0400 I SHARDING [rsSync] Marking collection as not sharded. [js_test:linearizable_read_concern] 2016-09-14T09:28:17.412-0400 d20013| 2016-09-14T09:28:17.411-0400 I SHARDING [rsSync] Marking collection as not sharded. [js_test:linearizable_read_concern] 2016-09-14T09:28:17.412-0400 d20013| 2016-09-14T09:28:17.411-0400 I REPL [rsSync] transition to primary complete; database writes are now permitted
In addition, the utility of this log message is minimal, so it should not be getting logged at the default log level (0).
- is duplicated by
-
SERVER-26184 Seems like some sharding hooks are running without sharding enabled
-
- Closed
-
-
SERVER-26172 Better logging in MetadataManager::refreshActiveMetadata
-
- Closed
-