Investigate if initial sync workload is actually timing initial sync or write load

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.1
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The write load takes up almost the entirety of the test. It's very likely that the test is timing the write load and that the initial sync finished much earlier.

      [2017/11/21 11:33:24.538] Adding last node
[2017/11/21 11:33:24.538] Write load started
[2017/11/21 11:33:24.538] connecting to: mongodb://10.2.0.200:27017/
[2017/11/21 11:33:24.538] MongoDB server version: 3.7.0-63-ga7064e0
[2017/11/21 11:36:55.415] Write load finished
...
[2017/11/21 11:36:58.419] Third node now successfully in SECONDARY state.
[2017/11/21 11:36:58.419] Tue Nov 21 2017 11:36:58 GMT+0000 (UTC)
[2017/11/21 11:36:58.419] Total time for initial sync: 213.919 seconds, or 213.915 seconds
[2017/11/21 11:36:58.460] >>> initialsync_dbs_1_colls_1_writeload_true : 24508.715915837303 1

            Assignee:
            David Daly (Inactive)
            Reporter:
            Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: