2017-02-14T18:40:40.775+0000 I CONTROL  [initandlisten] MongoDB starting : pid=24713 port=27017 dbpath=/var/lib/mongodb 64-bit host=1c
2017-02-14T18:40:40.775+0000 I CONTROL  [initandlisten] db version v3.0.12
2017-02-14T18:40:40.775+0000 I CONTROL  [initandlisten] git version: 33934938e0e95d534cebbaff656cde916b9c3573
2017-02-14T18:40:40.775+0000 I CONTROL  [initandlisten] build info: Linux ip-10-229-66-2 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 BOOST_LIB_VERSION=1_49
2017-02-14T18:40:40.775+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2017-02-14T18:40:40.775+0000 I CONTROL  [initandlisten] options: { config: "/etc/mongod.conf", net: { port: 27017 }, replication: { replSetName: "production-rs" }, security: { authorization: "disabled" }, storage: { dbPath: "/var/lib/mongodb", journal: { enabled: true } }, systemLog: { component: { replication: { verbosity: 5 } }, destination: "file", logAppend: true, path: "/var/log/mongodb/mongod.log" } }
2017-02-14T18:40:40.818+0000 I JOURNAL  [initandlisten] journal dir=/var/lib/mongodb/journal
2017-02-14T18:40:40.818+0000 I JOURNAL  [initandlisten] recover : no journal files present, no recovery needed
2017-02-14T18:40:40.892+0000 I JOURNAL  [durability] Durability thread started
2017-02-14T18:40:40.892+0000 I JOURNAL  [journal writer] Journal writer thread started
2017-02-14T18:40:40.906+0000 I STORAGE  [initandlisten] WARNING: the collection 'boulderbrands_production.data_cubes' lacks a unique index on _id. This index is needed for replication to function properly
2017-02-14T18:40:40.906+0000 I STORAGE  [initandlisten] 	 To fix this, you need to create a unique index on _id. See http://dochub.mongodb.org/core/build-replica-set-indexes
2017-02-14T18:40:40.946+0000 I NETWORK  [initandlisten] waiting for connections on port 27017
2017-02-14T18:40:40.948+0000 D REPL     [ReplExecNetThread-0] thread starting
2017-02-14T18:40:40.950+0000 W REPL     [ReplicationExecutor] Failed to load timestamp of most recently applied operation; NoMatchingDocument Did not find any entries in local.oplog.rs
2017-02-14T18:40:40.950+0000 I REPL     [ReplicationExecutor] New replica set config in use: { _id: "production-rs", version: 117276, members: [ { _id: 1, host: "1e-26:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 }, { _id: 2, host: "1c:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 } ], settings: { chainingAllowed: true, heartbeatTimeoutSecs: 10, getLastErrorModes: {}, getLastErrorDefaults: { w: 1, wtimeout: 0 } } }
2017-02-14T18:40:40.950+0000 I REPL     [ReplicationExecutor] This node is 1c:27017 in the config
2017-02-14T18:40:40.950+0000 I REPL     [ReplicationExecutor] transition to STARTUP2
2017-02-14T18:40:40.950+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:40:40.950Z
2017-02-14T18:40:40.950+0000 I REPL     [ReplicationExecutor] Starting replication applier threads
2017-02-14T18:40:40.951+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:40:40.951+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57327 #1 (1 connection now open)
2017-02-14T18:40:40.951+0000 I REPL     [rsSync] initial sync pending
2017-02-14T18:40:40.952+0000 I REPL     [rsSync] no valid sync sources found in current replset to do an initial sync
2017-02-14T18:40:40.952+0000 I NETWORK  [conn1] end connection 10.45.51.252:57327 (0 connections now open)
2017-02-14T18:40:40.953+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:40:40.953+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:40:40.953+0000 I REPL     [ReplicationExecutor] Member 1e-26:27017 is now in state SECONDARY
2017-02-14T18:40:40.953+0000 D REPL     [ReplicationExecutor] Not standing for election because node has no applied oplog entries; member is not currently a secondary; member is more than 10 seconds behind the most up-to-date member (mask 0x4A); my last optime is 0:0 and the newest is 58a34bf9:1
2017-02-14T18:40:40.953+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:40:42.953Z
2017-02-14T18:40:40.953+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57328 #2 (1 connection now open)
2017-02-14T18:40:40.954+0000 I REPL     [ReplicationExecutor] replSetElect voting yea for 1e-26:27017 (1)
2017-02-14T18:40:41.952+0000 I REPL     [rsSync] initial sync pending
2017-02-14T18:40:41.952+0000 I REPL     [rsSync] no valid sync sources found in current replset to do an initial sync
2017-02-14T18:40:42.952+0000 I REPL     [rsSync] initial sync pending
2017-02-14T18:40:42.953+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:40:42.953+0000 I REPL     [rsSync] no valid sync sources found in current replset to do an initial sync
2017-02-14T18:40:42.954+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:40:42.954+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:40:42.954+0000 I REPL     [ReplicationExecutor] Member 1e-26:27017 is now in state PRIMARY
2017-02-14T18:40:42.954+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:40:44.954Z
2017-02-14T18:40:43.953+0000 I REPL     [rsSync] initial sync pending
2017-02-14T18:40:43.953+0000 I REPL     [ReplicationExecutor] syncing from: 1e-26:27017
2017-02-14T18:40:43.958+0000 I REPL     [rsSync] initial sync drop all databases
2017-02-14T18:40:43.958+0000 I STORAGE  [rsSync] dropAllDatabasesExceptLocal 4
2017-02-14T18:40:43.961+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T18:40:43.961+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T18:40:43.966+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T18:40:43.966+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T18:40:43.978+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T18:40:43.978+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T18:40:43.983+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T18:40:43.983+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T18:40:43.987+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T18:40:43.987+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T18:40:43.992+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T18:40:43.992+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T18:40:44.000+0000 I REPL     [rsSync] initial sync clone all databases
2017-02-14T18:40:44.006+0000 I REPL     [rsSync] initial sync cloning db: admin
2017-02-14T18:40:44.011+0000 I REPL     [rsSync] initial sync cloning db: aryzta_production
2017-02-14T18:40:44.015+0000 I INDEX    [rsSync] allocating new ns file /var/lib/mongodb/aryzta_production.ns, filling with zeroes...
2017-02-14T18:40:44.088+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/aryzta_production.0, filling with zeroes...
2017-02-14T18:40:44.088+0000 I STORAGE  [FileAllocator] creating directory /var/lib/mongodb/_tmp
2017-02-14T18:40:44.090+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/aryzta_production.0, size: 64MB,  took 0 secs
2017-02-14T18:40:44.166+0000 I INDEX    [rsSync] build index on: aryzta_production.access_logs properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.access_logs" }
2017-02-14T18:40:44.166+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.169+0000 I INDEX    [rsSync] build index done.  scanned 1818 total records. 0 secs
2017-02-14T18:40:44.169+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/aryzta_production.1, filling with zeroes...
2017-02-14T18:40:44.170+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/aryzta_production.1, size: 128MB,  took 0 secs
2017-02-14T18:40:44.172+0000 I INDEX    [rsSync] build index on: aryzta_production.events properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.events" }
2017-02-14T18:40:44.172+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.172+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:40:44.173+0000 I INDEX    [rsSync] build index on: aryzta_production.warehouser_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.warehouser_pings" }
2017-02-14T18:40:44.173+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.174+0000 I INDEX    [rsSync] build index done.  scanned 115 total records. 0 secs
2017-02-14T18:40:44.179+0000 I INDEX    [rsSync] build index on: aryzta_production.action_dispatch.session.mongo_mapper_store.sessions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.action_dispatch.session.mongo_mapper_store.sessions" }
2017-02-14T18:40:44.179+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.181+0000 I INDEX    [rsSync] build index done.  scanned 1465 total records. 0 secs
2017-02-14T18:40:44.183+0000 I INDEX    [rsSync] build index on: aryzta_production.users properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.users" }
2017-02-14T18:40:44.183+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.183+0000 I INDEX    [rsSync] build index done.  scanned 5 total records. 0 secs
2017-02-14T18:40:44.184+0000 I INDEX    [rsSync] build index on: aryzta_production.configurations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.configurations" }
2017-02-14T18:40:44.184+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.184+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:40:44.186+0000 I INDEX    [rsSync] build index on: aryzta_production.organizations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.organizations" }
2017-02-14T18:40:44.186+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.186+0000 I INDEX    [rsSync] build index done.  scanned 46 total records. 0 secs
2017-02-14T18:40:44.187+0000 I INDEX    [rsSync] build index on: aryzta_production.accounts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.accounts" }
2017-02-14T18:40:44.187+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.187+0000 I INDEX    [rsSync] build index done.  scanned 5 total records. 0 secs
2017-02-14T18:40:44.188+0000 I INDEX    [rsSync] build index on: aryzta_production.attachment_types properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.attachment_types" }
2017-02-14T18:40:44.188+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.188+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T18:40:44.189+0000 I INDEX    [rsSync] build index on: aryzta_production.investment_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.investment_categories" }
2017-02-14T18:40:44.189+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.189+0000 I INDEX    [rsSync] build index done.  scanned 5 total records. 0 secs
2017-02-14T18:40:44.190+0000 I INDEX    [rsSync] build index on: aryzta_production.investment_sizes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.investment_sizes" }
2017-02-14T18:40:44.190+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.190+0000 I INDEX    [rsSync] build index done.  scanned 5 total records. 0 secs
2017-02-14T18:40:44.192+0000 I INDEX    [rsSync] build index on: aryzta_production.field_audit.audit_records properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.field_audit.audit_records" }
2017-02-14T18:40:44.192+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.192+0000 I INDEX    [rsSync] build index done.  scanned 55 total records. 0 secs
2017-02-14T18:40:44.198+0000 I INDEX    [rsSync] build index on: aryzta_production.investments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.investments" }
2017-02-14T18:40:44.198+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.198+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T18:40:44.199+0000 I INDEX    [rsSync] build index on: aryzta_production.user_dimensions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.user_dimensions" }
2017-02-14T18:40:44.199+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.199+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:40:44.200+0000 I INDEX    [rsSync] build index on: aryzta_production.custom_fields properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.custom_fields" }
2017-02-14T18:40:44.201+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.201+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:40:44.202+0000 I INDEX    [rsSync] build index on: aryzta_production.approval_rounds properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.approval_rounds" }
2017-02-14T18:40:44.202+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.202+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:40:44.203+0000 I INDEX    [rsSync] build index on: aryzta_production.authorities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.authorities" }
2017-02-14T18:40:44.203+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.203+0000 I INDEX    [rsSync] build index done.  scanned 8 total records. 0 secs
2017-02-14T18:40:44.204+0000 I INDEX    [rsSync] build index on: aryzta_production.approval_routes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.approval_routes" }
2017-02-14T18:40:44.204+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.204+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T18:40:44.206+0000 I INDEX    [rsSync] build index on: aryzta_production.budgets properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.budgets" }
2017-02-14T18:40:44.206+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.206+0000 I INDEX    [rsSync] build index done.  scanned 40 total records. 0 secs
2017-02-14T18:40:44.236+0000 I INDEX    [rsSync] build index on: aryzta_production.data_cubes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.data_cubes" }
2017-02-14T18:40:44.236+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.238+0000 I INDEX    [rsSync] build index done.  scanned 1368 total records. 0 secs
2017-02-14T18:40:44.240+0000 I INDEX    [rsSync] build index on: aryzta_production.approvals properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.approvals" }
2017-02-14T18:40:44.240+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.240+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:40:44.241+0000 I INDEX    [rsSync] build index on: aryzta_production.activities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.activities" }
2017-02-14T18:40:44.241+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.241+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T18:40:44.242+0000 I INDEX    [rsSync] build index on: aryzta_production.comments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.comments" }
2017-02-14T18:40:44.242+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.242+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:40:44.243+0000 I INDEX    [rsSync] build index on: aryzta_production.forecasts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.forecasts" }
2017-02-14T18:40:44.243+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.243+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:40:44.244+0000 I INDEX    [rsSync] build index on: aryzta_production.warehouse_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.warehouse_pings" }
2017-02-14T18:40:44.244+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.244+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:40:44.245+0000 I INDEX    [rsSync] build index on: aryzta_production.shared_views properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.shared_views" }
2017-02-14T18:40:44.245+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.245+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:40:44.246+0000 I INDEX    [rsSync] build index on: aryzta_production.cost_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.cost_categories" }
2017-02-14T18:40:44.246+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.246+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:40:44.247+0000 I INDEX    [rsSync] build index on: aryzta_production.progress_reports properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.progress_reports" }
2017-02-14T18:40:44.247+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.247+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:40:44.249+0000 I INDEX    [rsSync] build index on: aryzta_production.attachments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.attachments" }
2017-02-14T18:40:44.249+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.249+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:40:44.250+0000 I INDEX    [rsSync] build index on: aryzta_production.progress properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.progress" }
2017-02-14T18:40:44.250+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.250+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T18:40:44.250+0000 I REPL     [rsSync] initial sync cloning db: axia_production
2017-02-14T18:40:44.254+0000 I INDEX    [rsSync] allocating new ns file /var/lib/mongodb/axia_production.ns, filling with zeroes...
2017-02-14T18:40:44.345+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/axia_production.0, filling with zeroes...
2017-02-14T18:40:44.346+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/axia_production.0, size: 64MB,  took 0 secs
2017-02-14T18:40:44.507+0000 I INDEX    [rsSync] build index on: axia_production.access_logs properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.access_logs" }
2017-02-14T18:40:44.507+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.514+0000 I INDEX    [rsSync] build index done.  scanned 2689 total records. 0 secs
2017-02-14T18:40:44.514+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/axia_production.1, filling with zeroes...
2017-02-14T18:40:44.515+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/axia_production.1, size: 128MB,  took 0 secs
2017-02-14T18:40:44.517+0000 I INDEX    [rsSync] build index on: axia_production.events properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.events" }
2017-02-14T18:40:44.517+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.517+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T18:40:44.519+0000 I INDEX    [rsSync] build index on: axia_production.warehouser_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.warehouser_pings" }
2017-02-14T18:40:44.519+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.519+0000 I INDEX    [rsSync] build index done.  scanned 115 total records. 0 secs
2017-02-14T18:40:44.542+0000 I INDEX    [rsSync] build index on: axia_production.action_dispatch.session.mongo_mapper_store.sessions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.action_dispatch.session.mongo_mapper_store.sessions" }
2017-02-14T18:40:44.542+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.552+0000 I INDEX    [rsSync] build index done.  scanned 6075 total records. 0 secs
2017-02-14T18:40:44.554+0000 I INDEX    [rsSync] build index on: axia_production.users properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.users" }
2017-02-14T18:40:44.554+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.554+0000 I INDEX    [rsSync] build index done.  scanned 7 total records. 0 secs
2017-02-14T18:40:44.556+0000 I INDEX    [rsSync] build index on: axia_production.configurations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.configurations" }
2017-02-14T18:40:44.556+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.556+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:40:44.557+0000 I INDEX    [rsSync] build index on: axia_production.organizations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.organizations" }
2017-02-14T18:40:44.557+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.558+0000 I INDEX    [rsSync] build index done.  scanned 17 total records. 0 secs
2017-02-14T18:40:44.559+0000 I INDEX    [rsSync] build index on: axia_production.investment_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.investment_categories" }
2017-02-14T18:40:44.559+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.559+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T18:40:44.571+0000 I INDEX    [rsSync] build index on: axia_production.investments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.investments" }
2017-02-14T18:40:44.571+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.571+0000 I INDEX    [rsSync] build index done.  scanned 7 total records. 0 secs
2017-02-14T18:40:44.586+0000 I INDEX    [rsSync] build index on: axia_production.field_audit.audit_records properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.field_audit.audit_records" }
2017-02-14T18:40:44.586+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.589+0000 I INDEX    [rsSync] build index done.  scanned 1510 total records. 0 secs
2017-02-14T18:40:44.590+0000 I INDEX    [rsSync] build index on: axia_production.user_dimensions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.user_dimensions" }
2017-02-14T18:40:44.590+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.590+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:40:44.594+0000 I INDEX    [rsSync] build index on: axia_production.custom_fields properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.custom_fields" }
2017-02-14T18:40:44.594+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.594+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:40:44.595+0000 I INDEX    [rsSync] build index on: axia_production.approval_rounds properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.approval_rounds" }
2017-02-14T18:40:44.595+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.595+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:40:44.597+0000 I INDEX    [rsSync] build index on: axia_production.authorities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.authorities" }
2017-02-14T18:40:44.597+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.597+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T18:40:44.598+0000 I INDEX    [rsSync] build index on: axia_production.approval_routes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.approval_routes" }
2017-02-14T18:40:44.598+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.598+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:40:44.601+0000 I INDEX    [rsSync] build index on: axia_production.budgets properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.budgets" }
2017-02-14T18:40:44.601+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.601+0000 I INDEX    [rsSync] build index done.  scanned 26 total records. 0 secs
2017-02-14T18:40:44.761+0000 I INDEX    [rsSync] build index on: axia_production.data_cubes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.data_cubes" }
2017-02-14T18:40:44.761+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.770+0000 I INDEX    [rsSync] build index done.  scanned 4900 total records. 0 secs
2017-02-14T18:40:44.771+0000 I INDEX    [rsSync] build index on: axia_production.accounts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.accounts" }
2017-02-14T18:40:44.771+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.771+0000 I INDEX    [rsSync] build index done.  scanned 8 total records. 0 secs
2017-02-14T18:40:44.773+0000 I INDEX    [rsSync] build index on: axia_production.shared_views properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.shared_views" }
2017-02-14T18:40:44.773+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.773+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T18:40:44.774+0000 I INDEX    [rsSync] build index on: axia_production.approvals properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.approvals" }
2017-02-14T18:40:44.774+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.774+0000 I INDEX    [rsSync] build index done.  scanned 7 total records. 0 secs
2017-02-14T18:40:44.776+0000 I INDEX    [rsSync] build index on: axia_production.activities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.activities" }
2017-02-14T18:40:44.776+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.776+0000 I INDEX    [rsSync] build index done.  scanned 39 total records. 0 secs
2017-02-14T18:40:44.777+0000 I INDEX    [rsSync] build index on: axia_production.comments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.comments" }
2017-02-14T18:40:44.777+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.777+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:40:44.778+0000 I INDEX    [rsSync] build index on: axia_production.pdf_render_jobs properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.pdf_render_jobs" }
2017-02-14T18:40:44.778+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.778+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:40:44.780+0000 I INDEX    [rsSync] build index on: axia_production.access_nonces properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.access_nonces" }
2017-02-14T18:40:44.780+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.780+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:40:44.781+0000 I INDEX    [rsSync] build index on: axia_production.fs.files properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.fs.files" }
2017-02-14T18:40:44.781+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.781+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T18:40:44.831+0000 I INDEX    [rsSync] build index on: axia_production.fs.chunks properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.fs.chunks" }
2017-02-14T18:40:44.831+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.831+0000 I INDEX    [rsSync] build index done.  scanned 24 total records. 0 secs
2017-02-14T18:40:44.832+0000 I INDEX    [rsSync] build index on: axia_production.vendors properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.vendors" }
2017-02-14T18:40:44.832+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.833+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:40:44.834+0000 I INDEX    [rsSync] build index on: axia_production.attachment_types properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.attachment_types" }
2017-02-14T18:40:44.834+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.834+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T18:40:44.836+0000 I INDEX    [rsSync] build index on: axia_production.forecasts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.forecasts" }
2017-02-14T18:40:44.836+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.836+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T18:40:44.837+0000 I INDEX    [rsSync] build index on: axia_production.user_guides properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.user_guides" }
2017-02-14T18:40:44.837+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.837+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:40:44.838+0000 I INDEX    [rsSync] build index on: axia_production.cost_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.cost_categories" }
2017-02-14T18:40:44.838+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.838+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T18:40:44.840+0000 I INDEX    [rsSync] build index on: axia_production.attachments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.attachments" }
2017-02-14T18:40:44.840+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.840+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T18:40:44.841+0000 I INDEX    [rsSync] build index on: axia_production.warehouse_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.warehouse_pings" }
2017-02-14T18:40:44.841+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.841+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:40:44.842+0000 I INDEX    [rsSync] build index on: axia_production.payments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.payments" }
2017-02-14T18:40:44.842+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.842+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:40:44.843+0000 I INDEX    [rsSync] build index on: axia_production.timelines properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.timelines" }
2017-02-14T18:40:44.843+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.843+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:40:44.844+0000 I INDEX    [rsSync] build index on: axia_production.progress_reports properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.progress_reports" }
2017-02-14T18:40:44.844+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.844+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:40:44.844+0000 I REPL     [rsSync] initial sync cloning db: boulderbrands_production
2017-02-14T18:40:44.848+0000 I INDEX    [rsSync] allocating new ns file /var/lib/mongodb/boulderbrands_production.ns, filling with zeroes...
2017-02-14T18:40:44.953+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.0, filling with zeroes...
2017-02-14T18:40:44.954+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:40:44.954+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.0, size: 64MB,  took 0 secs
2017-02-14T18:40:44.955+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:40:44.955+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:40:44.955+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:40:46.955Z
2017-02-14T18:40:44.964+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.1, filling with zeroes...
2017-02-14T18:40:44.965+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.1, size: 128MB,  took 0 secs
2017-02-14T18:40:44.969+0000 I INDEX    [rsSync] build index on: boulderbrands_production.events properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.events" }
2017-02-14T18:40:44.969+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:44.971+0000 I INDEX    [rsSync] build index done.  scanned 796 total records. 0 secs
2017-02-14T18:40:45.077+0000 I INDEX    [rsSync] build index on: boulderbrands_production.access_logs properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.access_logs" }
2017-02-14T18:40:45.077+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:45.092+0000 I INDEX    [rsSync] build index done.  scanned 5433 total records. 0 secs
2017-02-14T18:40:45.094+0000 I INDEX    [rsSync] build index on: boulderbrands_production.warehouser_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.warehouser_pings" }
2017-02-14T18:40:45.094+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:45.094+0000 I INDEX    [rsSync] build index done.  scanned 115 total records. 0 secs
2017-02-14T18:40:45.301+0000 I INDEX    [rsSync] build index on: boulderbrands_production.action_dispatch.session.mongo_mapper_store.sessions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.action_dispatch.session.mongo_mapper_store.sessions" }
2017-02-14T18:40:45.301+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:45.437+0000 I INDEX    [rsSync] build index done.  scanned 67286 total records. 0 secs
2017-02-14T18:40:45.441+0000 I INDEX    [rsSync] build index on: boulderbrands_production.users properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.users" }
2017-02-14T18:40:45.441+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:45.441+0000 I INDEX    [rsSync] build index done.  scanned 60 total records. 0 secs
2017-02-14T18:40:45.442+0000 I INDEX    [rsSync] build index on: boulderbrands_production.configurations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.configurations" }
2017-02-14T18:40:45.442+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:45.442+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:40:45.443+0000 I INDEX    [rsSync] build index on: boulderbrands_production.organizations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.organizations" }
2017-02-14T18:40:45.443+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:45.443+0000 I INDEX    [rsSync] build index done.  scanned 9 total records. 0 secs
2017-02-14T18:40:45.444+0000 I INDEX    [rsSync] build index on: boulderbrands_production.accounts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.accounts" }
2017-02-14T18:40:45.444+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:45.445+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T18:40:45.446+0000 I INDEX    [rsSync] build index on: boulderbrands_production.attachment_types properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.attachment_types" }
2017-02-14T18:40:45.446+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:45.446+0000 I INDEX    [rsSync] build index done.  scanned 7 total records. 0 secs
2017-02-14T18:40:45.447+0000 I INDEX    [rsSync] build index on: boulderbrands_production.user_guides properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.user_guides" }
2017-02-14T18:40:45.447+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:45.447+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:40:45.448+0000 I INDEX    [rsSync] build index on: boulderbrands_production.investment_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.investment_categories" }
2017-02-14T18:40:45.448+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:45.448+0000 I INDEX    [rsSync] build index done.  scanned 10 total records. 0 secs
2017-02-14T18:40:45.450+0000 I INDEX    [rsSync] build index on: boulderbrands_production.investment_sizes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.investment_sizes" }
2017-02-14T18:40:45.450+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:45.450+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T18:40:45.554+0000 I INDEX    [rsSync] build index on: boulderbrands_production.field_audit.audit_records properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.field_audit.audit_records" }
2017-02-14T18:40:45.554+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:45.572+0000 I INDEX    [rsSync] build index done.  scanned 9289 total records. 0 secs
2017-02-14T18:40:45.574+0000 I INDEX    [rsSync] build index on: boulderbrands_production.cost_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.cost_categories" }
2017-02-14T18:40:45.574+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:45.574+0000 I INDEX    [rsSync] build index done.  scanned 11 total records. 0 secs
2017-02-14T18:40:45.658+0000 I INDEX    [rsSync] build index on: boulderbrands_production.investments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.investments" }
2017-02-14T18:40:45.658+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:45.660+0000 I INDEX    [rsSync] build index done.  scanned 780 total records. 0 secs
2017-02-14T18:40:45.663+0000 I INDEX    [rsSync] build index on: boulderbrands_production.vendors properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.vendors" }
2017-02-14T18:40:45.663+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:45.663+0000 I INDEX    [rsSync] build index done.  scanned 95 total records. 0 secs
2017-02-14T18:40:45.666+0000 I INDEX    [rsSync] build index on: boulderbrands_production.approval_rounds properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.approval_rounds" }
2017-02-14T18:40:45.666+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:45.666+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:40:45.667+0000 I INDEX    [rsSync] build index on: boulderbrands_production.authorities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.authorities" }
2017-02-14T18:40:45.667+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:45.667+0000 I INDEX    [rsSync] build index done.  scanned 11 total records. 0 secs
2017-02-14T18:40:45.668+0000 I INDEX    [rsSync] build index on: boulderbrands_production.approval_routes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.approval_routes" }
2017-02-14T18:40:45.668+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:45.668+0000 I INDEX    [rsSync] build index done.  scanned 8 total records. 0 secs
2017-02-14T18:40:45.696+0000 I INDEX    [rsSync] build index on: boulderbrands_production.approvals properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.approvals" }
2017-02-14T18:40:45.696+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:45.702+0000 I INDEX    [rsSync] build index done.  scanned 3483 total records. 0 secs
2017-02-14T18:40:45.759+0000 I INDEX    [rsSync] build index on: boulderbrands_production.activities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.activities" }
2017-02-14T18:40:45.759+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:40:45.782+0000 I INDEX    [rsSync] build index done.  scanned 8558 total records. 0 secs
2017-02-14T18:40:45.875+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.2, filling with zeroes...
2017-02-14T18:40:45.877+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.2, size: 256MB,  took 0.001 secs
2017-02-14T18:40:46.955+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:40:46.956+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:40:46.956+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:40:46.956+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:40:48.956Z
2017-02-14T18:40:48.956+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:40:48.957+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:40:48.957+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:40:48.957+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:40:50.957Z
2017-02-14T18:40:50.957+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:40:50.958+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:40:50.958+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:40:50.958+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:40:52.958Z
2017-02-14T18:40:52.959+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:40:52.960+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:40:52.960+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:40:52.960+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:40:54.960Z
2017-02-14T18:40:54.960+0000 I NETWORK  [conn2] end connection 10.45.51.252:57328 (0 connections now open)
2017-02-14T18:40:54.960+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:40:54.961+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57329 #3 (1 connection now open)
2017-02-14T18:40:54.961+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:40:54.961+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:40:54.961+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:40:56.961Z
2017-02-14T18:40:56.961+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:40:56.962+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:40:56.962+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:40:56.962+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:40:58.962Z
2017-02-14T18:40:58.962+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:40:58.963+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:40:58.963+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:40:58.963+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:00.963Z
2017-02-14T18:41:00.964+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:00.965+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:00.965+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:00.965+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:02.965Z
2017-02-14T18:41:02.965+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:02.966+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:02.966+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:02.966+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:04.966Z
2017-02-14T18:41:04.966+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:04.967+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:04.967+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:04.967+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:06.967Z
2017-02-14T18:41:06.968+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:06.969+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:06.969+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:06.969+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:08.969Z
2017-02-14T18:41:08.969+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:08.970+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:08.970+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:08.970+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:10.970Z
2017-02-14T18:41:10.970+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:10.972+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:10.972+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:10.972+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:12.972Z
2017-02-14T18:41:12.972+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:12.973+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:12.973+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:12.973+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:14.973Z
2017-02-14T18:41:14.974+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:14.975+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:14.975+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:14.975+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:16.975Z
2017-02-14T18:41:16.975+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:16.976+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:16.976+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:16.976+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:18.976Z
2017-02-14T18:41:18.976+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:18.977+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:18.977+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:18.977+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:20.977Z
2017-02-14T18:41:20.977+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:20.978+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:20.978+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:20.978+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:22.978Z
2017-02-14T18:41:22.978+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:22.979+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:22.979+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:22.979+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:24.979Z
2017-02-14T18:41:24.978+0000 I NETWORK  [conn3] end connection 10.45.51.252:57329 (0 connections now open)
2017-02-14T18:41:24.979+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57333 #4 (1 connection now open)
2017-02-14T18:41:24.979+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:24.980+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:24.980+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:24.980+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:26.980Z
2017-02-14T18:41:26.980+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:26.981+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:26.982+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:26.982+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:28.982Z
2017-02-14T18:41:28.982+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:28.983+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:28.983+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:28.983+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:30.983Z
2017-02-14T18:41:30.983+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:30.984+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:30.984+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:30.984+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:32.984Z
2017-02-14T18:41:32.984+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:32.985+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:32.985+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:32.985+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:34.985Z
2017-02-14T18:41:34.986+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:34.987+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:34.987+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:34.987+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:36.987Z
2017-02-14T18:41:36.987+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:36.988+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:36.988+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:36.988+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:38.988Z
2017-02-14T18:41:38.988+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:38.989+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:38.989+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:38.989+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:40.989Z
2017-02-14T18:41:40.989+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:40.992+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:40.992+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:40.992+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:42.992Z
2017-02-14T18:41:42.992+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:42.993+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:42.993+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:42.993+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:44.993Z
2017-02-14T18:41:44.993+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:44.994+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:44.994+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:44.994+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:46.994Z
2017-02-14T18:41:45.527+0000 I STORAGE  [rsSync] clone boulderbrands_production.data_cubes 21503
2017-02-14T18:41:46.994+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:46.995+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:46.995+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:46.995+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:48.995Z
2017-02-14T18:41:47.033+0000 I STORAGE  [rsSync] 21512 objects cloned so far from collection boulderbrands_production.data_cubes
2017-02-14T18:41:48.996+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:48.996+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:48.997+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:48.997+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:50.997Z
2017-02-14T18:41:50.997+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:50.998+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:50.998+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:50.998+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:52.998Z
2017-02-14T18:41:52.998+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:52.999+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:52.999+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:52.999+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:54.999Z
2017-02-14T18:41:54.998+0000 I NETWORK  [conn4] end connection 10.45.51.252:57333 (0 connections now open)
2017-02-14T18:41:54.999+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57336 #5 (1 connection now open)
2017-02-14T18:41:54.999+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:55.000+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:55.000+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:55.000+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:57.000Z
2017-02-14T18:41:57.000+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:57.001+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:57.001+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:57.001+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:41:59.001Z
2017-02-14T18:41:59.001+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:41:59.002+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:41:59.003+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:41:59.003+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:01.003Z
2017-02-14T18:42:01.003+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:01.004+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:01.004+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:01.004+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:03.004Z
2017-02-14T18:42:03.004+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:03.005+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:03.005+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:03.005+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:05.005Z
2017-02-14T18:42:05.005+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:05.006+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:05.006+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:05.006+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:07.006Z
2017-02-14T18:42:07.006+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:07.007+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:07.007+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:07.008+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:09.007Z
2017-02-14T18:42:09.007+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:09.008+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:09.008+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:09.008+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:11.008Z
2017-02-14T18:42:11.008+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:11.010+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:11.010+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:11.010+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:13.010Z
2017-02-14T18:42:13.010+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:13.011+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:13.011+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:13.011+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:15.011Z
2017-02-14T18:42:15.011+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:15.012+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:15.012+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:15.012+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:17.012Z
2017-02-14T18:42:16.155+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.3, filling with zeroes...
2017-02-14T18:42:16.157+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.3, size: 512MB,  took 0.001 secs
2017-02-14T18:42:17.012+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:17.013+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:17.013+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:17.013+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:19.013Z
2017-02-14T18:42:19.013+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:19.014+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:19.014+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:19.014+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:21.014Z
2017-02-14T18:42:21.015+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:21.016+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:21.016+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:21.016+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:23.016Z
2017-02-14T18:42:23.016+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:23.017+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:23.017+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:23.017+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:25.017Z
2017-02-14T18:42:25.017+0000 I NETWORK  [conn5] end connection 10.45.51.252:57336 (0 connections now open)
2017-02-14T18:42:25.017+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:25.018+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57340 #6 (1 connection now open)
2017-02-14T18:42:25.018+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:25.018+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:25.018+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:27.018Z
2017-02-14T18:42:27.018+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:27.019+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:27.019+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:27.019+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:29.019Z
2017-02-14T18:42:29.020+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:29.021+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:29.021+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:29.021+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:31.021Z
2017-02-14T18:42:31.021+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:31.022+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:31.022+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:31.022+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:33.022Z
2017-02-14T18:42:33.022+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:33.023+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:33.023+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:33.023+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:35.023Z
2017-02-14T18:42:35.024+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:35.025+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:35.025+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:35.025+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:37.025Z
2017-02-14T18:42:37.025+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:37.026+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:37.026+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:37.026+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:39.026Z
2017-02-14T18:42:39.026+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:39.028+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:39.028+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:39.028+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:41.028Z
2017-02-14T18:42:41.028+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:41.030+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:41.030+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:41.030+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:43.030Z
2017-02-14T18:42:43.030+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:43.031+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:43.031+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:43.031+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:45.031Z
2017-02-14T18:42:45.031+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:45.032+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:45.032+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:45.032+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:47.032Z
2017-02-14T18:42:47.032+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:47.033+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:47.033+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:47.033+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:49.033Z
2017-02-14T18:42:47.521+0000 I STORAGE  [rsSync] clone boulderbrands_production.data_cubes 23935
2017-02-14T18:42:49.033+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:49.033+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:49.034+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:49.034+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:51.034Z
2017-02-14T18:42:49.829+0000 I STORAGE  [rsSync] 24052 objects cloned so far from collection boulderbrands_production.data_cubes
2017-02-14T18:42:51.034+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:51.035+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:51.035+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:51.035+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:53.035Z
2017-02-14T18:42:53.035+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:53.036+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:53.036+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:53.036+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:55.036Z
2017-02-14T18:42:55.036+0000 I NETWORK  [conn6] end connection 10.45.51.252:57340 (0 connections now open)
2017-02-14T18:42:55.036+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:55.037+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57343 #7 (1 connection now open)
2017-02-14T18:42:55.037+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:55.037+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:55.037+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:57.037Z
2017-02-14T18:42:57.038+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:57.039+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:57.039+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:57.039+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:42:59.039Z
2017-02-14T18:42:59.039+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:42:59.040+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:42:59.040+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:42:59.040+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:01.040Z
2017-02-14T18:43:01.040+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:01.041+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:01.041+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:01.041+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:03.041Z
2017-02-14T18:43:03.041+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:03.042+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:03.042+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:03.042+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:05.042Z
2017-02-14T18:43:05.043+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:05.044+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:05.044+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:05.044+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:07.044Z
2017-02-14T18:43:07.044+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:07.045+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:07.045+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:07.045+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:09.045Z
2017-02-14T18:43:09.045+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:09.046+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:09.046+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:09.046+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:11.046Z
2017-02-14T18:43:11.046+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:11.048+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:11.049+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:11.049+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:13.049Z
2017-02-14T18:43:13.049+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:13.050+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:13.050+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:13.050+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:15.050Z
2017-02-14T18:43:15.050+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:15.051+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:15.051+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:15.051+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:17.051Z
2017-02-14T18:43:17.051+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:17.052+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:17.052+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:17.052+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:19.052Z
2017-02-14T18:43:19.052+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:19.053+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:19.053+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:19.053+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:21.053Z
2017-02-14T18:43:21.054+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:21.055+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:21.055+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:21.055+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:23.055Z
2017-02-14T18:43:23.055+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:23.056+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:23.056+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:23.056+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:25.056Z
2017-02-14T18:43:25.056+0000 I NETWORK  [conn7] end connection 10.45.51.252:57343 (0 connections now open)
2017-02-14T18:43:25.056+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:25.057+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57347 #8 (1 connection now open)
2017-02-14T18:43:25.057+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:25.057+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:25.057+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:27.057Z
2017-02-14T18:43:27.057+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:27.058+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:27.058+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:27.058+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:29.058Z
2017-02-14T18:43:29.059+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:29.060+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:29.060+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:29.060+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:31.060Z
2017-02-14T18:43:31.060+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:31.061+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:31.061+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:31.061+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:33.061Z
2017-02-14T18:43:33.061+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:33.062+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:33.062+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:33.062+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:35.062Z
2017-02-14T18:43:35.062+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:35.063+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:35.063+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:35.063+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:37.063Z
2017-02-14T18:43:37.064+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:37.065+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:37.065+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:37.065+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:39.065Z
2017-02-14T18:43:39.065+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:39.066+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:39.066+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:39.066+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:41.066Z
2017-02-14T18:43:41.066+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:41.068+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:41.069+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:41.069+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:43.069Z
2017-02-14T18:43:43.069+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:43.070+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:43.070+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:43.070+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:45.070Z
2017-02-14T18:43:45.070+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:45.071+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:45.071+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:45.071+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:47.071Z
2017-02-14T18:43:47.072+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:47.072+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:47.073+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:47.073+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:49.073Z
2017-02-14T18:43:49.073+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:49.074+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:49.074+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:49.074+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:51.074Z
2017-02-14T18:43:49.280+0000 I STORAGE  [rsSync] clone boulderbrands_production.data_cubes 26239
2017-02-14T18:43:51.074+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:51.075+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:51.075+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:51.075+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:53.075Z
2017-02-14T18:43:51.427+0000 I STORAGE  [rsSync] 26338 objects cloned so far from collection boulderbrands_production.data_cubes
2017-02-14T18:43:53.075+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:53.076+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:53.076+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:53.076+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:55.076Z
2017-02-14T18:43:55.075+0000 I NETWORK  [conn8] end connection 10.45.51.252:57347 (0 connections now open)
2017-02-14T18:43:55.077+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:55.077+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57350 #9 (1 connection now open)
2017-02-14T18:43:55.078+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:55.078+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:55.078+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:57.078Z
2017-02-14T18:43:57.078+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:57.079+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:57.079+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:57.079+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:43:59.079Z
2017-02-14T18:43:59.079+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:43:59.080+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:43:59.080+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:43:59.080+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:01.080Z
2017-02-14T18:44:01.080+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:01.082+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:01.082+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:01.082+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:03.082Z
2017-02-14T18:44:03.082+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:03.083+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:03.083+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:03.083+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:05.083Z
2017-02-14T18:44:05.083+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:05.084+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:05.084+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:05.084+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:07.084Z
2017-02-14T18:44:07.084+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:07.085+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:07.085+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:07.085+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:09.085Z
2017-02-14T18:44:07.845+0000 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:60870 #10 (2 connections now open)
2017-02-14T18:44:09.086+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:09.087+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:09.087+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:09.087+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:11.087Z
2017-02-14T18:44:11.087+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:11.089+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:11.089+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:11.089+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:13.089Z
2017-02-14T18:44:13.089+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:13.090+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:13.090+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:13.090+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:15.090Z
2017-02-14T18:44:13.586+0000 I NETWORK  [conn10] end connection 127.0.0.1:60870 (1 connection now open)
2017-02-14T18:44:15.090+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:15.092+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:15.092+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:15.092+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:17.092Z
2017-02-14T18:44:17.092+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:17.093+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:17.093+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:17.093+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:19.093Z
2017-02-14T18:44:19.093+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:19.094+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:19.094+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:19.094+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:21.094Z
2017-02-14T18:44:21.094+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:21.095+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:21.095+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:21.095+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:23.095Z
2017-02-14T18:44:23.095+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:23.096+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:23.096+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:23.096+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:25.096Z
2017-02-14T18:44:25.095+0000 I NETWORK  [conn9] end connection 10.45.51.252:57350 (0 connections now open)
2017-02-14T18:44:25.096+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57354 #11 (1 connection now open)
2017-02-14T18:44:25.096+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:25.097+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:25.097+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:25.097+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:27.097Z
2017-02-14T18:44:27.097+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:27.098+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:27.098+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:27.098+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:29.098Z
2017-02-14T18:44:29.099+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:29.100+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:29.100+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:29.100+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:31.100Z
2017-02-14T18:44:31.100+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:31.101+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:31.101+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:31.101+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:33.101Z
2017-02-14T18:44:33.101+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:33.102+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:33.102+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:33.102+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:35.102Z
2017-02-14T18:44:35.102+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:35.103+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:35.104+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:35.104+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:37.103Z
2017-02-14T18:44:37.103+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:37.104+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:37.104+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:37.104+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:39.104Z
2017-02-14T18:44:39.104+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:39.105+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:39.105+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:39.105+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:41.105Z
2017-02-14T18:44:40.635+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.4, filling with zeroes...
2017-02-14T18:44:40.638+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.4, size: 1024MB,  took 0.002 secs
2017-02-14T18:44:41.105+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:41.107+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:41.107+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:41.107+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:43.107Z
2017-02-14T18:44:43.107+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:43.108+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:43.108+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:43.108+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:45.108Z
2017-02-14T18:44:45.108+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:45.109+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:45.109+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:45.109+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:47.109Z
2017-02-14T18:44:47.109+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:47.110+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:47.110+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:47.110+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:49.110Z
2017-02-14T18:44:49.111+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:49.112+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:49.112+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:49.112+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:51.112Z
2017-02-14T18:44:51.112+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:51.113+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:51.113+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:51.113+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:53.113Z
2017-02-14T18:44:52.368+0000 I STORAGE  [rsSync] clone boulderbrands_production.data_cubes 28287
2017-02-14T18:44:53.113+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:53.114+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:53.114+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:53.114+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:55.114Z
2017-02-14T18:44:54.431+0000 I STORAGE  [rsSync] 28370 objects cloned so far from collection boulderbrands_production.data_cubes
2017-02-14T18:44:55.114+0000 I NETWORK  [conn11] end connection 10.45.51.252:57354 (0 connections now open)
2017-02-14T18:44:55.114+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:55.115+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57357 #12 (1 connection now open)
2017-02-14T18:44:55.115+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:55.115+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:55.115+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:57.115Z
2017-02-14T18:44:57.116+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:57.117+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:57.117+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:57.117+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:44:59.117Z
2017-02-14T18:44:59.117+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:44:59.118+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:44:59.118+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:44:59.118+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:01.118Z
2017-02-14T18:45:01.118+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:01.120+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:01.120+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:01.120+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:03.120Z
2017-02-14T18:45:03.120+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:03.121+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:03.121+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:03.121+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:05.121Z
2017-02-14T18:45:05.121+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:05.122+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:05.122+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:05.122+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:07.122Z
2017-02-14T18:45:07.123+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:07.124+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:07.124+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:07.124+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:09.124Z
2017-02-14T18:45:09.124+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:09.125+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:09.125+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:09.125+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:11.125Z
2017-02-14T18:45:11.125+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:11.127+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:11.127+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:11.127+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:13.127Z
2017-02-14T18:45:13.127+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:13.128+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:13.128+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:13.128+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:15.128Z
2017-02-14T18:45:15.128+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:15.133+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:15.133+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:15.133+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:17.133Z
2017-02-14T18:45:17.133+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:17.134+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:17.134+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:17.135+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:19.134Z
2017-02-14T18:45:19.134+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:19.137+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:19.137+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:19.137+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:21.137Z
2017-02-14T18:45:21.137+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:21.138+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:21.138+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:21.138+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:23.138Z
2017-02-14T18:45:23.139+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:23.141+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:23.142+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:23.142+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:25.142Z
2017-02-14T18:45:25.142+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:25.142+0000 I NETWORK  [conn12] end connection 10.45.51.252:57357 (0 connections now open)
2017-02-14T18:45:25.143+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:25.143+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:25.143+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:27.143Z
2017-02-14T18:45:25.143+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57361 #13 (1 connection now open)
2017-02-14T18:45:27.143+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:27.144+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:27.144+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:27.144+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:29.144Z
2017-02-14T18:45:29.144+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:29.145+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:29.145+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:29.145+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:31.145Z
2017-02-14T18:45:31.145+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:31.146+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:31.146+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:31.146+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:33.146Z
2017-02-14T18:45:33.146+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:33.147+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:33.147+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:33.147+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:35.147Z
2017-02-14T18:45:35.147+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:35.148+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:35.148+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:35.148+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:37.148Z
2017-02-14T18:45:37.148+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:37.149+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:37.149+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:37.149+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:39.149Z
2017-02-14T18:45:39.149+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:39.150+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:39.150+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:39.150+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:41.150Z
2017-02-14T18:45:41.150+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:41.152+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:41.152+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:41.152+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:43.152Z
2017-02-14T18:45:43.152+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:43.153+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:43.153+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:43.154+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:45.153Z
2017-02-14T18:45:45.153+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:45.154+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:45.154+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:45.154+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:47.154Z
2017-02-14T18:45:47.154+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:47.155+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:47.155+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:47.155+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:49.155Z
2017-02-14T18:45:49.156+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:49.157+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:49.157+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:49.157+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:51.157Z
2017-02-14T18:45:51.157+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:51.158+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:51.158+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:51.158+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:53.158Z
2017-02-14T18:45:53.158+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:53.159+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:53.159+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:53.159+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:55.159Z
2017-02-14T18:45:55.159+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:55.160+0000 I NETWORK  [conn13] end connection 10.45.51.252:57361 (0 connections now open)
2017-02-14T18:45:55.160+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:55.161+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:55.161+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:57.161Z
2017-02-14T18:45:55.161+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57364 #14 (1 connection now open)
2017-02-14T18:45:56.497+0000 I STORAGE  [rsSync] clone boulderbrands_production.data_cubes 30591
2017-02-14T18:45:57.161+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:57.162+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:57.162+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:57.162+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:45:59.162Z
2017-02-14T18:45:57.474+0000 I STORAGE  [rsSync] 30656 objects cloned so far from collection boulderbrands_production.data_cubes
2017-02-14T18:45:59.163+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:45:59.164+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:45:59.164+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:45:59.164+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:01.164Z
2017-02-14T18:46:01.164+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:01.165+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:01.165+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:01.165+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:03.165Z
2017-02-14T18:46:03.165+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:03.166+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:03.166+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:03.166+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:05.166Z
2017-02-14T18:46:05.167+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:05.168+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:05.168+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:05.168+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:07.168Z
2017-02-14T18:46:07.168+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:07.169+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:07.169+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:07.169+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:09.169Z
2017-02-14T18:46:09.169+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:09.170+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:09.170+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:09.170+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:11.170Z
2017-02-14T18:46:11.170+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:11.173+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:11.173+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:11.173+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:13.173Z
2017-02-14T18:46:13.173+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:13.174+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:13.174+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:13.174+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:15.174Z
2017-02-14T18:46:15.174+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:15.175+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:15.175+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:15.175+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:17.175Z
2017-02-14T18:46:17.175+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:17.176+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:17.176+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:17.176+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:19.176Z
2017-02-14T18:46:19.176+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:19.177+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:19.177+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:19.177+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:21.177Z
2017-02-14T18:46:21.178+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:21.179+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:21.179+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:21.179+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:23.179Z
2017-02-14T18:46:23.179+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:23.180+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:23.180+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:23.180+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:25.180Z
2017-02-14T18:46:25.179+0000 I NETWORK  [conn14] end connection 10.45.51.252:57364 (0 connections now open)
2017-02-14T18:46:25.180+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57368 #15 (1 connection now open)
2017-02-14T18:46:25.180+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:25.181+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:25.181+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:25.181+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:27.181Z
2017-02-14T18:46:27.181+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:27.182+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:27.182+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:27.182+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:29.182Z
2017-02-14T18:46:29.182+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:29.183+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:29.184+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:29.184+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:31.184Z
2017-02-14T18:46:31.184+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:31.185+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:31.185+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:31.185+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:33.185Z
2017-02-14T18:46:33.185+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:33.186+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:33.186+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:33.186+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:35.186Z
2017-02-14T18:46:35.186+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:35.187+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:35.187+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:35.187+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:37.187Z
2017-02-14T18:46:37.188+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:37.189+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:37.189+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:37.189+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:39.189Z
2017-02-14T18:46:39.189+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:39.190+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:39.190+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:39.190+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:41.190Z
2017-02-14T18:46:41.190+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:41.192+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:41.192+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:41.192+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:43.192Z
2017-02-14T18:46:43.193+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:43.194+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:43.194+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:43.194+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:45.194Z
2017-02-14T18:46:45.194+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:45.195+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:45.195+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:45.195+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:47.195Z
2017-02-14T18:46:47.195+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:47.196+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:47.196+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:47.196+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:49.196Z
2017-02-14T18:46:49.196+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:49.197+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:49.197+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:49.198+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:51.197Z
2017-02-14T18:46:51.197+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:51.198+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:51.198+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:51.198+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:53.198Z
2017-02-14T18:46:53.198+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:53.199+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:53.199+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:53.199+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:55.199Z
2017-02-14T18:46:55.199+0000 I NETWORK  [conn15] end connection 10.45.51.252:57368 (0 connections now open)
2017-02-14T18:46:55.199+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:55.200+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57371 #16 (1 connection now open)
2017-02-14T18:46:55.200+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:55.200+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:55.200+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:57.200Z
2017-02-14T18:46:57.200+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:57.201+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:57.202+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:57.202+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:46:59.202Z
2017-02-14T18:46:57.367+0000 I STORAGE  [rsSync] clone boulderbrands_production.data_cubes 32767
2017-02-14T18:46:59.202+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:46:59.203+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:46:59.203+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:46:59.203+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:01.203Z
2017-02-14T18:47:01.203+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:01.204+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:01.204+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:01.204+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:03.204Z
2017-02-14T18:47:01.461+0000 I STORAGE  [rsSync] 32942 objects cloned so far from collection boulderbrands_production.data_cubes
2017-02-14T18:47:03.204+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:03.205+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:03.206+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:03.206+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:05.206Z
2017-02-14T18:47:05.206+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:05.207+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:05.207+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:05.207+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:07.207Z
2017-02-14T18:47:07.207+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:07.208+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:07.208+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:07.208+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:09.208Z
2017-02-14T18:47:09.208+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:09.209+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:09.210+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:09.210+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:11.210Z
2017-02-14T18:47:11.210+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:11.212+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:11.212+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:11.212+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:13.212Z
2017-02-14T18:47:13.212+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:13.213+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:13.213+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:13.213+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:15.213Z
2017-02-14T18:47:15.213+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:15.214+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:15.214+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:15.214+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:17.214Z
2017-02-14T18:47:17.214+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:17.215+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:17.215+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:17.215+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:19.215Z
2017-02-14T18:47:19.215+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:19.216+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:19.216+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:19.216+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:21.216Z
2017-02-14T18:47:21.216+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:21.217+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:21.218+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:21.218+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:23.218Z
2017-02-14T18:47:23.218+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:23.219+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:23.219+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:23.219+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:25.219Z
2017-02-14T18:47:25.219+0000 I NETWORK  [conn16] end connection 10.45.51.252:57371 (0 connections now open)
2017-02-14T18:47:25.219+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:25.220+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57376 #17 (1 connection now open)
2017-02-14T18:47:25.220+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:25.220+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:25.220+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:27.220Z
2017-02-14T18:47:27.220+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:27.221+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:27.221+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:27.221+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:29.221Z
2017-02-14T18:47:29.221+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:29.223+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:29.223+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:29.223+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:31.223Z
2017-02-14T18:47:31.223+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:31.224+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:31.224+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:31.224+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:33.224Z
2017-02-14T18:47:33.225+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:33.226+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:33.226+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:33.226+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:35.226Z
2017-02-14T18:47:35.226+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:35.227+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:35.227+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:35.227+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:37.227Z
2017-02-14T18:47:37.227+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:37.228+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:37.228+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:37.228+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:39.228Z
2017-02-14T18:47:39.228+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:39.229+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:39.229+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:39.229+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:41.229Z
2017-02-14T18:47:41.230+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:41.232+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:41.232+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:41.232+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:43.232Z
2017-02-14T18:47:43.232+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:43.233+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:43.233+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:43.233+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:45.233Z
2017-02-14T18:47:45.233+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:45.234+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:45.234+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:45.234+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:47.234Z
2017-02-14T18:47:47.234+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:47.237+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:47.237+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:47.237+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:49.237Z
2017-02-14T18:47:49.237+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:49.238+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:49.238+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:49.238+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:51.238Z
2017-02-14T18:47:51.238+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:51.239+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:51.239+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:51.239+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:53.239Z
2017-02-14T18:47:53.239+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:53.240+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:53.240+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:53.240+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:55.240Z
2017-02-14T18:47:55.239+0000 I NETWORK  [conn17] end connection 10.45.51.252:57376 (0 connections now open)
2017-02-14T18:47:55.240+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57379 #18 (1 connection now open)
2017-02-14T18:47:55.240+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:55.241+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:55.241+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:55.241+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:57.241Z
2017-02-14T18:47:57.242+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:57.242+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:57.243+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:57.243+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:47:59.242Z
2017-02-14T18:47:59.242+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:47:59.243+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:47:59.243+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:47:59.243+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:01.243Z
2017-02-14T18:48:00.633+0000 I STORAGE  [rsSync] clone boulderbrands_production.data_cubes 34815
2017-02-14T18:48:01.243+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:01.244+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:01.244+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:01.244+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:03.244Z
2017-02-14T18:48:02.629+0000 I STORAGE  [rsSync] 34847 objects cloned so far from collection boulderbrands_production.data_cubes
2017-02-14T18:48:03.244+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:03.245+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:03.245+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:03.245+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:05.245Z
2017-02-14T18:48:05.246+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:05.247+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:05.247+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:05.247+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:07.247Z
2017-02-14T18:48:07.247+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:07.248+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:07.248+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:07.248+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:09.248Z
2017-02-14T18:48:09.248+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:09.249+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:09.249+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:09.249+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:11.249Z
2017-02-14T18:48:11.249+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:11.251+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:11.251+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:11.251+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:13.251Z
2017-02-14T18:48:13.251+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:13.252+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:13.252+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:13.252+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:15.252Z
2017-02-14T18:48:15.252+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:15.253+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:15.253+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:15.253+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:17.253Z
2017-02-14T18:48:17.253+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:17.255+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:17.255+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:17.255+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:19.255Z
2017-02-14T18:48:19.256+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:19.257+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:19.257+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:19.257+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:21.257Z
2017-02-14T18:48:21.257+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:21.258+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:21.258+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:21.258+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:23.258Z
2017-02-14T18:48:23.258+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:23.259+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:23.259+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:23.259+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:25.259Z
2017-02-14T18:48:25.258+0000 I NETWORK  [conn18] end connection 10.45.51.252:57379 (0 connections now open)
2017-02-14T18:48:25.259+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57384 #19 (1 connection now open)
2017-02-14T18:48:25.259+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:25.260+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:25.260+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:25.260+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:27.260Z
2017-02-14T18:48:27.260+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:27.261+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:27.261+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:27.261+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:29.261Z
2017-02-14T18:48:29.262+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:29.263+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:29.263+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:29.263+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:31.263Z
2017-02-14T18:48:31.263+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:31.264+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:31.264+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:31.264+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:33.264Z
2017-02-14T18:48:33.264+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:33.265+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:33.265+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:33.265+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:35.265Z
2017-02-14T18:48:35.265+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:35.266+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:35.267+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:35.267+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:37.267Z
2017-02-14T18:48:37.267+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:37.268+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:37.268+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:37.268+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:39.268Z
2017-02-14T18:48:39.268+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:39.269+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:39.269+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:39.269+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:41.269Z
2017-02-14T18:48:41.269+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:41.271+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:41.271+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:41.271+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:43.271Z
2017-02-14T18:48:43.271+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:43.272+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:43.272+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:43.272+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:45.272Z
2017-02-14T18:48:45.272+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:45.273+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:45.273+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:45.273+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:47.273Z
2017-02-14T18:48:47.273+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:47.274+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:47.274+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:47.274+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:49.274Z
2017-02-14T18:48:49.274+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:49.275+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:49.275+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:49.275+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:51.275Z
2017-02-14T18:48:51.276+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:51.277+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:51.277+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:51.277+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:53.277Z
2017-02-14T18:48:53.277+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:53.278+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:53.278+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:53.278+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:55.278Z
2017-02-14T18:48:55.278+0000 I NETWORK  [conn19] end connection 10.45.51.252:57384 (0 connections now open)
2017-02-14T18:48:55.278+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:55.279+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57387 #20 (1 connection now open)
2017-02-14T18:48:55.279+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:55.279+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:55.279+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:57.279Z
2017-02-14T18:48:57.279+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:57.280+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:57.280+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:57.281+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:48:59.280Z
2017-02-14T18:48:59.280+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:48:59.281+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:48:59.281+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:48:59.281+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:01.281Z
2017-02-14T18:49:01.282+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:01.283+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:01.283+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:01.283+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:03.283Z
2017-02-14T18:49:03.283+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:03.284+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:03.284+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:03.284+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:05.284Z
2017-02-14T18:49:05.284+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:05.285+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:05.285+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:05.285+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:07.285Z
2017-02-14T18:49:06.720+0000 I STORAGE  [rsSync] clone boulderbrands_production.data_cubes 36479
2017-02-14T18:49:06.720+0000 I STORAGE  [rsSync] 36498 objects cloned so far from collection boulderbrands_production.data_cubes
2017-02-14T18:49:07.286+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:07.287+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:07.287+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:07.287+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:09.287Z
2017-02-14T18:49:09.287+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:09.288+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:09.288+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:09.288+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:11.288Z
2017-02-14T18:49:11.288+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:11.290+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:11.290+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:11.290+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:13.290Z
2017-02-14T18:49:13.290+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:13.291+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:13.291+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:13.291+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:15.291Z
2017-02-14T18:49:15.291+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:15.292+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:15.292+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:15.292+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:17.292Z
2017-02-14T18:49:17.292+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:17.293+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:17.293+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:17.293+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:19.293Z
2017-02-14T18:49:19.293+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:19.294+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:19.295+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:19.295+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:21.295Z
2017-02-14T18:49:21.295+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:21.296+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:21.296+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:21.296+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:23.296Z
2017-02-14T18:49:23.296+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:23.297+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:23.297+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:23.297+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:25.297Z
2017-02-14T18:49:25.297+0000 I NETWORK  [conn20] end connection 10.45.51.252:57387 (0 connections now open)
2017-02-14T18:49:25.297+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:25.298+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57391 #21 (1 connection now open)
2017-02-14T18:49:25.298+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:25.298+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:25.298+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:27.298Z
2017-02-14T18:49:27.298+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:27.300+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:27.300+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:27.300+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:29.300Z
2017-02-14T18:49:29.300+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:29.301+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:29.301+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:29.301+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:31.301Z
2017-02-14T18:49:31.301+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:31.302+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:31.302+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:31.302+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:33.302Z
2017-02-14T18:49:33.302+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:33.303+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:33.303+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:33.303+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:35.303Z
2017-02-14T18:49:35.304+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:35.305+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:35.305+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:35.305+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:37.305Z
2017-02-14T18:49:37.305+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:37.306+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:37.306+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:37.306+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:39.306Z
2017-02-14T18:49:39.306+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:39.307+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:39.308+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:39.308+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:41.308Z
2017-02-14T18:49:41.308+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:41.310+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:41.310+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:41.310+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:43.310Z
2017-02-14T18:49:43.310+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:43.311+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:43.311+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:43.311+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:45.311Z
2017-02-14T18:49:45.311+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:45.312+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:45.312+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:45.312+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:47.312Z
2017-02-14T18:49:47.313+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:47.314+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:47.314+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:47.314+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:49.314Z
2017-02-14T18:49:49.314+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:49.315+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:49.315+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:49.315+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:51.315Z
2017-02-14T18:49:51.315+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:51.316+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:51.316+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:51.316+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:53.316Z
2017-02-14T18:49:53.316+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:53.317+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:53.317+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:53.317+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:55.317Z
2017-02-14T18:49:55.316+0000 I NETWORK  [conn21] end connection 10.45.51.252:57391 (0 connections now open)
2017-02-14T18:49:55.317+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57394 #22 (1 connection now open)
2017-02-14T18:49:55.317+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:55.318+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:55.318+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:55.318+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:57.318Z
2017-02-14T18:49:57.319+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:57.320+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:57.320+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:57.320+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:49:59.320Z
2017-02-14T18:49:59.320+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:49:59.321+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:49:59.321+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:49:59.321+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:01.321Z
2017-02-14T18:50:01.321+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:01.322+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:01.322+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:01.322+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:03.322Z
2017-02-14T18:50:03.322+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:03.323+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:03.324+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:03.324+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:05.323Z
2017-02-14T18:50:05.323+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:05.324+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:05.324+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:05.324+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:07.324Z
2017-02-14T18:50:07.324+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:07.325+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:07.325+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:07.325+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:09.325Z
2017-02-14T18:50:09.207+0000 I STORAGE  [rsSync] clone boulderbrands_production.data_cubes 38399
2017-02-14T18:50:09.207+0000 I STORAGE  [rsSync] 38403 objects cloned so far from collection boulderbrands_production.data_cubes
2017-02-14T18:50:09.325+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:09.326+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:09.326+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:09.326+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:11.326Z
2017-02-14T18:50:11.327+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:11.329+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:11.329+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:11.329+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:13.329Z
2017-02-14T18:50:13.329+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:13.330+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:13.330+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:13.330+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:15.330Z
2017-02-14T18:50:15.330+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:15.331+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:15.331+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:15.331+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:17.331Z
2017-02-14T18:50:17.331+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:17.332+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:17.332+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:17.332+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:19.332Z
2017-02-14T18:50:19.333+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:19.334+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:19.334+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:19.334+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:21.334Z
2017-02-14T18:50:21.334+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:21.335+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:21.335+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:21.335+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:23.335Z
2017-02-14T18:50:23.335+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:23.336+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:23.336+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:23.336+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:25.336Z
2017-02-14T18:50:25.336+0000 I NETWORK  [conn22] end connection 10.45.51.252:57394 (0 connections now open)
2017-02-14T18:50:25.337+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:25.337+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57398 #23 (1 connection now open)
2017-02-14T18:50:25.338+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:25.338+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:25.338+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:27.338Z
2017-02-14T18:50:27.338+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:27.339+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:27.339+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:27.339+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:29.339Z
2017-02-14T18:50:29.339+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:29.340+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:29.340+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:29.340+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:31.340Z
2017-02-14T18:50:31.340+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:31.344+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:31.345+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:31.345+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:33.345Z
2017-02-14T18:50:33.346+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:33.346+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:33.347+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:33.347+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:35.347Z
2017-02-14T18:50:35.347+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:35.348+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:35.348+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:35.348+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:37.348Z
2017-02-14T18:50:37.348+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:37.349+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:37.349+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:37.349+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:39.349Z
2017-02-14T18:50:39.349+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:39.350+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:39.350+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:39.350+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:41.350Z
2017-02-14T18:50:41.351+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:41.353+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:41.353+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:41.353+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:43.353Z
2017-02-14T18:50:43.353+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:43.354+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:43.354+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:43.354+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:45.354Z
2017-02-14T18:50:45.354+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:45.355+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:45.355+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:45.355+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:47.355Z
2017-02-14T18:50:47.102+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.5, filling with zeroes...
2017-02-14T18:50:47.105+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.5, size: 2047MB,  took 0.003 secs
2017-02-14T18:50:47.355+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:47.356+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:47.356+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:47.356+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:49.356Z
2017-02-14T18:50:49.356+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:49.357+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:49.358+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:49.358+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:51.358Z
2017-02-14T18:50:51.358+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:51.359+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:51.359+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:51.359+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:53.359Z
2017-02-14T18:50:53.359+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:53.360+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:53.360+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:53.360+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:55.360Z
2017-02-14T18:50:55.358+0000 I NETWORK  [conn23] end connection 10.45.51.252:57398 (0 connections now open)
2017-02-14T18:50:55.359+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57401 #24 (1 connection now open)
2017-02-14T18:50:55.360+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:55.361+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:55.361+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:55.361+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:57.361Z
2017-02-14T18:50:57.361+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:57.362+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:57.362+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:57.362+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:50:59.362Z
2017-02-14T18:50:59.363+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:50:59.364+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:50:59.364+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:50:59.364+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:01.364Z
2017-02-14T18:51:01.364+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:01.365+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:01.365+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:01.365+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:03.365Z
2017-02-14T18:51:03.365+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:03.366+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:03.366+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:03.366+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:05.366Z
2017-02-14T18:51:05.366+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:05.367+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:05.367+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:05.367+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:07.367Z
2017-02-14T18:51:07.367+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:07.368+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:07.368+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:07.368+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:09.368Z
2017-02-14T18:51:09.368+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:09.369+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:09.369+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:09.369+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:11.369Z
2017-02-14T18:51:11.344+0000 I STORAGE  [rsSync] 40308 objects cloned so far from collection boulderbrands_production.data_cubes
2017-02-14T18:51:11.348+0000 I STORAGE  [rsSync] clone boulderbrands_production.data_cubes 40319
2017-02-14T18:51:11.369+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:11.371+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:11.371+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:11.371+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:13.371Z
2017-02-14T18:51:13.372+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:13.372+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:13.373+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:13.373+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:15.373Z
2017-02-14T18:51:15.373+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:15.374+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:15.374+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:15.374+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:17.374Z
2017-02-14T18:51:16.155+0000 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:60923 #25 (2 connections now open)
2017-02-14T18:51:17.374+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:17.375+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:17.375+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:17.375+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:19.375Z
2017-02-14T18:51:19.375+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:19.379+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:19.379+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:19.379+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:21.379Z
2017-02-14T18:51:21.380+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:21.381+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:21.381+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:21.381+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:23.381Z
2017-02-14T18:51:23.186+0000 I NETWORK  [conn25] end connection 127.0.0.1:60923 (1 connection now open)
2017-02-14T18:51:23.381+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:23.382+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:23.382+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:23.382+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:25.382Z
2017-02-14T18:51:25.378+0000 I NETWORK  [conn24] end connection 10.45.51.252:57401 (0 connections now open)
2017-02-14T18:51:25.379+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57405 #26 (1 connection now open)
2017-02-14T18:51:25.382+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:25.383+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:25.383+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:25.383+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:27.383Z
2017-02-14T18:51:27.383+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:27.384+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:27.384+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:27.384+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:29.384Z
2017-02-14T18:51:29.384+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:29.385+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:29.386+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:29.386+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:31.385Z
2017-02-14T18:51:31.385+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:31.386+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:31.386+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:31.386+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:33.386Z
2017-02-14T18:51:33.386+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:33.387+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:33.387+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:33.387+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:35.387Z
2017-02-14T18:51:35.387+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:35.388+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:35.388+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:35.388+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:37.388Z
2017-02-14T18:51:37.388+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:37.389+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:37.389+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:37.389+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:39.389Z
2017-02-14T18:51:39.390+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:39.391+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:39.391+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:39.391+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:41.391Z
2017-02-14T18:51:41.391+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:41.393+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:41.393+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:41.393+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:43.393Z
2017-02-14T18:51:43.393+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:43.394+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:43.394+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:43.394+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:45.394Z
2017-02-14T18:51:45.394+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:45.395+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:45.395+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:45.395+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:47.395Z
2017-02-14T18:51:47.395+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:47.396+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:47.396+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:47.396+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:49.396Z
2017-02-14T18:51:49.396+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:49.397+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:49.397+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:49.397+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:51.397Z
2017-02-14T18:51:51.397+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:51.398+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:51.398+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:51.398+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:53.398Z
2017-02-14T18:51:53.398+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:53.399+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:53.399+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:53.399+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:55.399Z
2017-02-14T18:51:55.397+0000 I NETWORK  [conn26] end connection 10.45.51.252:57405 (0 connections now open)
2017-02-14T18:51:55.398+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57408 #27 (1 connection now open)
2017-02-14T18:51:55.399+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:55.399+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:55.400+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:55.400+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:57.400Z
2017-02-14T18:51:57.400+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:57.401+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:57.401+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:57.401+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:51:59.401Z
2017-02-14T18:51:59.401+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:51:59.402+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:51:59.402+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:51:59.402+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:01.402Z
2017-02-14T18:52:01.402+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:01.403+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:01.403+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:01.403+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:03.403Z
2017-02-14T18:52:03.404+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:03.406+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:03.406+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:03.407+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:05.406Z
2017-02-14T18:52:05.406+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:05.407+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:05.407+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:05.407+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:07.407Z
2017-02-14T18:52:07.407+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:07.408+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:07.408+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:07.408+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:09.408Z
2017-02-14T18:52:09.408+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:09.409+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:09.409+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:09.409+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:11.409Z
2017-02-14T18:52:11.410+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:11.412+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:11.412+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:11.412+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:13.412Z
2017-02-14T18:52:13.056+0000 I STORAGE  [rsSync] clone boulderbrands_production.data_cubes 42495
2017-02-14T18:52:13.412+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:13.413+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:13.413+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:13.413+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:15.413Z
2017-02-14T18:52:14.797+0000 I STORAGE  [rsSync] 42594 objects cloned so far from collection boulderbrands_production.data_cubes
2017-02-14T18:52:15.414+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:15.415+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:15.415+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:15.415+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:17.415Z
2017-02-14T18:52:17.415+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:17.416+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:17.416+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:17.416+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:19.416Z
2017-02-14T18:52:19.416+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:19.417+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:19.417+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:19.417+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:21.417Z
2017-02-14T18:52:21.417+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:21.418+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:21.418+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:21.418+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:23.418Z
2017-02-14T18:52:23.419+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:23.420+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:23.420+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:23.420+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:25.420Z
2017-02-14T18:52:25.419+0000 I NETWORK  [conn27] end connection 10.45.51.252:57408 (0 connections now open)
2017-02-14T18:52:25.419+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57412 #28 (1 connection now open)
2017-02-14T18:52:25.420+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:25.421+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:25.421+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:25.421+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:27.421Z
2017-02-14T18:52:27.421+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:27.422+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:27.422+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:27.422+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:29.422Z
2017-02-14T18:52:29.422+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:29.423+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:29.423+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:29.423+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:31.423Z
2017-02-14T18:52:31.423+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:31.424+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:31.425+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:31.425+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:33.425Z
2017-02-14T18:52:33.425+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:33.426+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:33.426+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:33.426+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:35.426Z
2017-02-14T18:52:35.426+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:35.427+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:35.427+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:35.427+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:37.427Z
2017-02-14T18:52:37.427+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:37.428+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:37.428+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:37.428+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:39.428Z
2017-02-14T18:52:39.429+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:39.429+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:39.430+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:39.430+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:41.430Z
2017-02-14T18:52:41.430+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:41.432+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:41.432+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:41.432+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:43.432Z
2017-02-14T18:52:43.432+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:43.433+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:43.433+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:43.433+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:45.433Z
2017-02-14T18:52:45.433+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:45.434+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:45.434+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:45.434+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:47.434Z
2017-02-14T18:52:47.434+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:47.435+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:47.435+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:47.435+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:49.435Z
2017-02-14T18:52:49.435+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:49.436+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:49.436+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:49.436+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:51.436Z
2017-02-14T18:52:51.436+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:51.437+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:51.437+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:51.437+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:53.437Z
2017-02-14T18:52:53.437+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:53.439+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:53.439+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:53.439+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:55.439Z
2017-02-14T18:52:55.438+0000 I NETWORK  [conn28] end connection 10.45.51.252:57412 (0 connections now open)
2017-02-14T18:52:55.439+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:55.439+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57415 #29 (1 connection now open)
2017-02-14T18:52:55.440+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:55.440+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:55.440+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:57.440Z
2017-02-14T18:52:57.440+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:57.441+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:57.441+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:57.441+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:52:59.441Z
2017-02-14T18:52:59.441+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:52:59.442+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:52:59.442+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:52:59.442+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:01.442Z
2017-02-14T18:53:01.443+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:01.444+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:01.444+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:01.444+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:03.444Z
2017-02-14T18:53:03.444+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:03.445+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:03.445+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:03.445+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:05.445Z
2017-02-14T18:53:05.445+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:05.446+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:05.446+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:05.446+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:07.446Z
2017-02-14T18:53:07.447+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:07.448+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:07.448+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:07.448+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:09.448Z
2017-02-14T18:53:09.448+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:09.449+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:09.449+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:09.449+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:11.449Z
2017-02-14T18:53:11.449+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:11.451+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:11.451+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:11.451+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:13.451Z
2017-02-14T18:53:13.452+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:13.452+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:13.453+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:13.453+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:15.453Z
2017-02-14T18:53:14.056+0000 I STORAGE  [rsSync] clone boulderbrands_production.data_cubes 44287
2017-02-14T18:53:15.453+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:15.454+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:15.454+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:15.454+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:17.454Z
2017-02-14T18:53:16.121+0000 I STORAGE  [rsSync] 44372 objects cloned so far from collection boulderbrands_production.data_cubes
2017-02-14T18:53:17.454+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:17.455+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:17.455+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:17.455+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:19.455Z
2017-02-14T18:53:19.455+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:19.456+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:19.456+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:19.456+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:21.456Z
2017-02-14T18:53:21.456+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:21.457+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:21.457+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:21.457+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:23.457Z
2017-02-14T18:53:23.458+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:23.458+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:23.459+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:23.459+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:25.459Z
2017-02-14T18:53:25.458+0000 I NETWORK  [conn29] end connection 10.45.51.252:57415 (0 connections now open)
2017-02-14T18:53:25.458+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57419 #30 (1 connection now open)
2017-02-14T18:53:25.459+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:25.460+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:25.460+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:25.460+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:27.460Z
2017-02-14T18:53:27.460+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:27.461+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:27.461+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:27.461+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:29.461Z
2017-02-14T18:53:29.461+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:29.462+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:29.462+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:29.462+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:31.462Z
2017-02-14T18:53:31.462+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:31.463+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:31.464+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:31.464+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:33.464Z
2017-02-14T18:53:33.464+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:33.465+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:33.465+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:33.465+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:35.465Z
2017-02-14T18:53:35.465+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:35.466+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:35.466+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:35.466+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:37.466Z
2017-02-14T18:53:37.466+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:37.467+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:37.467+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:37.467+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:39.467Z
2017-02-14T18:53:39.468+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:39.469+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:39.469+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:39.469+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:41.469Z
2017-02-14T18:53:41.469+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:41.471+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:41.471+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:41.471+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:43.471Z
2017-02-14T18:53:43.471+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:43.472+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:43.472+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:43.472+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:45.472Z
2017-02-14T18:53:45.472+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:45.473+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:45.473+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:45.473+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:47.473Z
2017-02-14T18:53:47.474+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:47.475+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:47.475+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:47.475+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:49.475Z
2017-02-14T18:53:49.475+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:49.476+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:49.476+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:49.476+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:51.476Z
2017-02-14T18:53:51.476+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:51.477+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:51.477+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:51.477+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:53.477Z
2017-02-14T18:53:53.477+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:53.478+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:53.479+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:53.479+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:55.479Z
2017-02-14T18:53:55.478+0000 I NETWORK  [conn30] end connection 10.45.51.252:57419 (0 connections now open)
2017-02-14T18:53:55.479+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57422 #31 (1 connection now open)
2017-02-14T18:53:55.479+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:55.480+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:55.480+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:55.480+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:57.480Z
2017-02-14T18:53:57.480+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:57.481+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:57.481+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:57.481+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:53:59.481Z
2017-02-14T18:53:59.481+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:53:59.482+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:53:59.482+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:53:59.482+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:01.482Z
2017-02-14T18:54:01.482+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:01.483+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:01.484+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:01.484+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:03.484Z
2017-02-14T18:54:03.484+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:03.485+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:03.485+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:03.485+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:05.485Z
2017-02-14T18:54:05.485+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:05.486+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:05.486+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:05.486+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:07.486Z
2017-02-14T18:54:07.486+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:07.487+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:07.488+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:07.488+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:09.487Z
2017-02-14T18:54:09.487+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:09.488+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:09.488+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:09.488+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:11.488Z
2017-02-14T18:54:11.488+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:11.491+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:11.491+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:11.491+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:13.491Z
2017-02-14T18:54:13.491+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:13.492+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:13.492+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:13.492+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:15.492Z
2017-02-14T18:54:15.466+0000 I STORAGE  [rsSync] clone boulderbrands_production.data_cubes 46079
2017-02-14T18:54:15.492+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:15.493+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:15.493+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:15.493+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:17.493Z
2017-02-14T18:54:17.493+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:17.496+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:17.496+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:17.496+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:19.496Z
2017-02-14T18:54:19.496+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:19.497+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:19.497+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:19.498+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:21.497Z
2017-02-14T18:54:20.529+0000 I STORAGE  [rsSync] 46150 objects cloned so far from collection boulderbrands_production.data_cubes
2017-02-14T18:54:21.497+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:21.498+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:21.498+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:21.498+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:23.498Z
2017-02-14T18:54:23.498+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:23.499+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:23.499+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:23.499+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:25.499Z
2017-02-14T18:54:25.499+0000 I NETWORK  [conn31] end connection 10.45.51.252:57422 (0 connections now open)
2017-02-14T18:54:25.499+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:25.500+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57426 #32 (1 connection now open)
2017-02-14T18:54:25.500+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:25.500+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:25.500+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:27.500Z
2017-02-14T18:54:27.501+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:27.502+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:27.502+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:27.502+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:29.502Z
2017-02-14T18:54:29.502+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:29.503+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:29.503+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:29.503+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:31.503Z
2017-02-14T18:54:31.503+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:31.504+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:31.504+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:31.504+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:33.504Z
2017-02-14T18:54:33.504+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:33.505+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:33.505+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:33.506+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:35.505Z
2017-02-14T18:54:35.505+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:35.506+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:35.506+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:35.506+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:37.506Z
2017-02-14T18:54:37.506+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:37.507+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:37.507+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:37.507+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:39.507Z
2017-02-14T18:54:39.507+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:39.508+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:39.508+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:39.508+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:41.508Z
2017-02-14T18:54:41.509+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:41.511+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:41.511+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:41.511+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:43.511Z
2017-02-14T18:54:43.512+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:43.513+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:43.513+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:43.513+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:45.513Z
2017-02-14T18:54:45.513+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:45.514+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:45.514+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:45.514+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:47.514Z
2017-02-14T18:54:47.514+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:47.515+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:47.515+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:47.515+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:49.515Z
2017-02-14T18:54:49.515+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:49.518+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:49.518+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:49.518+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:51.518Z
2017-02-14T18:54:51.518+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:51.519+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:51.520+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:51.520+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:53.520Z
2017-02-14T18:54:53.520+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:53.521+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:53.521+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:53.521+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:55.521Z
2017-02-14T18:54:55.521+0000 I NETWORK  [conn32] end connection 10.45.51.252:57426 (0 connections now open)
2017-02-14T18:54:55.521+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:55.522+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57429 #33 (1 connection now open)
2017-02-14T18:54:55.522+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:55.522+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:55.522+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:57.522Z
2017-02-14T18:54:57.522+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:57.523+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:57.523+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:57.523+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:54:59.523Z
2017-02-14T18:54:59.523+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:54:59.524+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:54:59.525+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:54:59.525+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:01.525Z
2017-02-14T18:55:01.525+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:01.526+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:01.526+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:01.526+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:03.526Z
2017-02-14T18:55:03.526+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:03.527+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:03.527+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:03.527+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:05.527Z
2017-02-14T18:55:05.528+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:05.529+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:05.529+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:05.529+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:07.529Z
2017-02-14T18:55:07.529+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:07.530+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:07.530+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:07.530+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:09.530Z
2017-02-14T18:55:09.530+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:09.531+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:09.531+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:09.531+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:11.531Z
2017-02-14T18:55:11.531+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:11.533+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:11.533+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:11.533+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:13.533Z
2017-02-14T18:55:13.534+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:13.535+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:13.535+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:13.535+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:15.535Z
2017-02-14T18:55:15.524+0000 I STORAGE  [rsSync] clone boulderbrands_production.data_cubes 46975
2017-02-14T18:55:15.535+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:15.536+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:15.536+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:15.536+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:17.536Z
2017-02-14T18:55:17.536+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:17.537+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:17.537+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:17.537+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:19.537Z
2017-02-14T18:55:19.537+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:19.538+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:19.538+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:19.538+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:21.538Z
2017-02-14T18:55:21.449+0000 I STORAGE  [rsSync] 47039 objects cloned so far from collection boulderbrands_production.data_cubes
2017-02-14T18:55:21.539+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:21.539+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:21.540+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:21.540+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:23.540Z
2017-02-14T18:55:23.540+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:23.541+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:23.541+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:23.541+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:25.541Z
2017-02-14T18:55:25.540+0000 I NETWORK  [conn33] end connection 10.45.51.252:57429 (0 connections now open)
2017-02-14T18:55:25.541+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57433 #34 (1 connection now open)
2017-02-14T18:55:25.541+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:25.542+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:25.542+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:25.542+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:27.542Z
2017-02-14T18:55:27.542+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:27.544+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:27.545+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:27.545+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:29.545Z
2017-02-14T18:55:29.546+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:29.546+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:29.547+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:29.547+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:31.547Z
2017-02-14T18:55:31.547+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:31.548+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:31.548+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:31.548+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:33.548Z
2017-02-14T18:55:33.548+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:33.549+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:33.549+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:33.549+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:35.549Z
2017-02-14T18:55:35.549+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:35.550+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:35.550+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:35.550+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:37.550Z
2017-02-14T18:55:37.550+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:37.552+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:37.552+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:37.552+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:39.552Z
2017-02-14T18:55:39.552+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:39.560+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:39.560+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:39.560+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:41.560Z
2017-02-14T18:55:41.560+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:41.562+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:41.562+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:41.562+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:43.562Z
2017-02-14T18:55:43.562+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:43.563+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:43.563+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:43.563+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:45.563Z
2017-02-14T18:55:45.563+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:45.564+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:45.564+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:45.564+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:47.564Z
2017-02-14T18:55:47.564+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:47.565+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:47.565+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:47.565+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:49.565Z
2017-02-14T18:55:49.565+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:49.566+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:49.566+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:49.566+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:51.566Z
2017-02-14T18:55:51.567+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:51.568+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:51.568+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:51.568+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:53.568Z
2017-02-14T18:55:53.568+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:53.569+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:53.569+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:53.569+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:55.569Z
2017-02-14T18:55:55.569+0000 I NETWORK  [conn34] end connection 10.45.51.252:57433 (0 connections now open)
2017-02-14T18:55:55.569+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:55.570+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57436 #35 (1 connection now open)
2017-02-14T18:55:55.570+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:55.570+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:55.570+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:57.570Z
2017-02-14T18:55:57.570+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:57.571+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:57.572+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:57.572+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:55:59.572Z
2017-02-14T18:55:59.572+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:55:59.573+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:55:59.573+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:55:59.573+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:01.573Z
2017-02-14T18:56:01.573+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:01.574+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:01.574+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:01.574+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:03.574Z
2017-02-14T18:56:03.574+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:03.575+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:03.575+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:03.575+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:05.575Z
2017-02-14T18:56:05.576+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:05.577+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:05.577+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:05.577+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:07.577Z
2017-02-14T18:56:07.577+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:07.578+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:07.578+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:07.578+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:09.578Z
2017-02-14T18:56:09.578+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:09.579+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:09.579+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:09.579+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:11.579Z
2017-02-14T18:56:11.580+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:11.582+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:11.582+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:11.582+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:13.582Z
2017-02-14T18:56:13.582+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:13.583+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:13.583+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:13.583+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:15.583Z
2017-02-14T18:56:15.583+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:15.584+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:15.584+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:15.584+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:17.584Z
2017-02-14T18:56:17.584+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:17.585+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:17.586+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:17.586+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:19.585Z
2017-02-14T18:56:19.585+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:19.586+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:19.586+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:19.586+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:21.586Z
2017-02-14T18:56:21.487+0000 I STORAGE  [rsSync] clone boulderbrands_production.data_cubes 47999
2017-02-14T18:56:21.586+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:21.587+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:21.587+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:21.587+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:23.587Z
2017-02-14T18:56:23.587+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:23.588+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:23.588+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:23.588+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:25.588Z
2017-02-14T18:56:23.638+0000 I STORAGE  [rsSync] 48055 objects cloned so far from collection boulderbrands_production.data_cubes
2017-02-14T18:56:25.588+0000 I NETWORK  [conn35] end connection 10.45.51.252:57436 (0 connections now open)
2017-02-14T18:56:25.588+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:25.589+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57441 #36 (1 connection now open)
2017-02-14T18:56:25.589+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:25.589+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:25.589+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:27.589Z
2017-02-14T18:56:27.590+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:27.591+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:27.591+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:27.591+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:29.591Z
2017-02-14T18:56:29.591+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:29.592+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:29.592+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:29.592+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:31.592Z
2017-02-14T18:56:31.592+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:31.593+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:31.593+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:31.593+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:33.593Z
2017-02-14T18:56:33.593+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:33.595+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:33.595+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:33.595+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:35.595Z
2017-02-14T18:56:35.595+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:35.596+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:35.596+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:35.596+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:37.596Z
2017-02-14T18:56:37.596+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:37.597+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:37.597+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:37.597+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:39.597Z
2017-02-14T18:56:39.597+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:39.598+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:39.599+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:39.599+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:41.599Z
2017-02-14T18:56:41.599+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:41.601+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:41.601+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:41.601+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:43.601Z
2017-02-14T18:56:43.601+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:43.602+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:43.602+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:43.602+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:45.602Z
2017-02-14T18:56:45.602+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:45.603+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:45.603+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:45.604+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:47.603Z
2017-02-14T18:56:47.603+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:47.604+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:47.604+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:47.604+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:49.604Z
2017-02-14T18:56:49.604+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:49.605+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:49.605+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:49.605+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:51.605Z
2017-02-14T18:56:51.605+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:51.606+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:51.606+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:51.606+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:53.606Z
2017-02-14T18:56:53.606+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:53.608+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:53.608+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:53.608+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:55.608Z
2017-02-14T18:56:55.608+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:55.608+0000 I NETWORK  [conn36] end connection 10.45.51.252:57441 (0 connections now open)
2017-02-14T18:56:55.609+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:55.609+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:55.609+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:57.609Z
2017-02-14T18:56:55.609+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57444 #37 (1 connection now open)
2017-02-14T18:56:57.610+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:57.611+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:57.611+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:57.611+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:56:59.611Z
2017-02-14T18:56:59.611+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:56:59.612+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:56:59.612+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:56:59.612+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:01.612Z
2017-02-14T18:57:01.612+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:01.614+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:01.614+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:01.614+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:03.614Z
2017-02-14T18:57:03.614+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:03.615+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:03.615+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:03.615+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:05.615Z
2017-02-14T18:57:05.616+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:05.617+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:05.617+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:05.617+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:07.617Z
2017-02-14T18:57:07.617+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:07.618+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:07.618+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:07.618+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:09.618Z
2017-02-14T18:57:09.618+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:09.619+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:09.620+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:09.620+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:11.620Z
2017-02-14T18:57:11.620+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:11.622+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:11.622+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:11.622+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:13.622Z
2017-02-14T18:57:13.622+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:13.623+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:13.623+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:13.623+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:15.623Z
2017-02-14T18:57:15.624+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:15.625+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:15.625+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:15.625+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:17.625Z
2017-02-14T18:57:17.625+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:17.626+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:17.626+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:17.626+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:19.626Z
2017-02-14T18:57:19.626+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:19.627+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:19.627+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:19.627+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:21.627Z
2017-02-14T18:57:21.627+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:21.628+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:21.628+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:21.628+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:23.628Z
2017-02-14T18:57:23.628+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:23.629+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:23.629+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:23.629+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:25.629Z
2017-02-14T18:57:25.629+0000 I NETWORK  [conn37] end connection 10.45.51.252:57444 (0 connections now open)
2017-02-14T18:57:25.629+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:25.630+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57448 #38 (1 connection now open)
2017-02-14T18:57:25.630+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:25.630+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:25.630+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:27.630Z
2017-02-14T18:57:27.630+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:27.631+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:27.631+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:27.631+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:29.631Z
2017-02-14T18:57:28.084+0000 I STORAGE  [rsSync] clone boulderbrands_production.data_cubes 49023
2017-02-14T18:57:29.631+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:29.632+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:29.632+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:29.632+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:31.632Z
2017-02-14T18:57:31.633+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:31.634+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:31.634+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:31.634+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:33.634Z
2017-02-14T18:57:33.203+0000 I STORAGE  [rsSync] 49071 objects cloned so far from collection boulderbrands_production.data_cubes
2017-02-14T18:57:33.634+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:33.635+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:33.635+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:33.635+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:35.635Z
2017-02-14T18:57:35.635+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:35.636+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:35.636+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:35.636+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:37.636Z
2017-02-14T18:57:37.637+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:37.638+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:37.638+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:37.638+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:39.638Z
2017-02-14T18:57:39.638+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:39.639+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:39.639+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:39.639+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:41.639Z
2017-02-14T18:57:41.639+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:41.644+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:41.644+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:41.644+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:43.644Z
2017-02-14T18:57:43.645+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:43.645+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:43.646+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:43.646+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:45.646Z
2017-02-14T18:57:45.646+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:45.647+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:45.647+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:45.647+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:47.647Z
2017-02-14T18:57:47.647+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:47.648+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:47.648+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:47.648+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:49.648Z
2017-02-14T18:57:49.648+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:49.649+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:49.649+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:49.649+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:51.649Z
2017-02-14T18:57:51.649+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:51.650+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:51.650+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:51.650+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:53.650Z
2017-02-14T18:57:53.651+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:53.651+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:53.652+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:53.652+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:55.652Z
2017-02-14T18:57:55.650+0000 I NETWORK  [conn38] end connection 10.45.51.252:57448 (0 connections now open)
2017-02-14T18:57:55.651+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57451 #39 (1 connection now open)
2017-02-14T18:57:55.652+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:55.653+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:55.653+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:55.653+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:57.653Z
2017-02-14T18:57:57.653+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:57.654+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:57.654+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:57.654+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:57:59.654Z
2017-02-14T18:57:59.654+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:57:59.655+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:57:59.655+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:57:59.655+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:01.655Z
2017-02-14T18:58:01.656+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:01.657+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:01.657+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:01.657+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:03.657Z
2017-02-14T18:58:03.657+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:03.658+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:03.658+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:03.658+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:05.658Z
2017-02-14T18:58:05.658+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:05.659+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:05.659+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:05.659+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:07.659Z
2017-02-14T18:58:07.659+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:07.660+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:07.660+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:07.660+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:09.660Z
2017-02-14T18:58:09.660+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:09.661+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:09.661+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:09.661+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:11.661Z
2017-02-14T18:58:11.662+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:11.664+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:11.664+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:11.664+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:13.664Z
2017-02-14T18:58:13.664+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:13.665+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:13.665+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:13.665+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:15.665Z
2017-02-14T18:58:15.665+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:15.666+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:15.666+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:15.666+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:17.666Z
2017-02-14T18:58:17.666+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:17.667+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:17.667+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:17.667+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:19.667Z
2017-02-14T18:58:19.667+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:19.668+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:19.668+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:19.669+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:21.668Z
2017-02-14T18:58:21.668+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:21.669+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:21.669+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:21.669+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:23.669Z
2017-02-14T18:58:23.669+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:23.670+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:23.670+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:23.670+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:25.670Z
2017-02-14T18:58:25.669+0000 I NETWORK  [conn39] end connection 10.45.51.252:57451 (0 connections now open)
2017-02-14T18:58:25.670+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57455 #40 (1 connection now open)
2017-02-14T18:58:25.670+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:25.671+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:25.671+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:25.671+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:27.671Z
2017-02-14T18:58:27.671+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:27.672+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:27.672+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:27.672+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:29.672Z
2017-02-14T18:58:29.672+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:29.673+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:29.674+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:29.674+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:31.674Z
2017-02-14T18:58:31.674+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:31.675+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:31.675+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:31.675+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:33.675Z
2017-02-14T18:58:33.157+0000 I STORAGE  [rsSync] clone boulderbrands_production.data_cubes 50047
2017-02-14T18:58:33.675+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:33.676+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:33.676+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:33.676+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:35.676Z
2017-02-14T18:58:35.652+0000 I STORAGE  [rsSync] 50087 objects cloned so far from collection boulderbrands_production.data_cubes
2017-02-14T18:58:35.676+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:35.677+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:35.677+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:35.677+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:37.677Z
2017-02-14T18:58:37.677+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:37.678+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:37.678+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:37.678+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:39.678Z
2017-02-14T18:58:39.679+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:39.680+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:39.680+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:39.680+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:41.680Z
2017-02-14T18:58:41.680+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:41.682+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:41.682+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:41.682+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:43.682Z
2017-02-14T18:58:43.682+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:43.683+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:43.683+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:43.683+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:45.683Z
2017-02-14T18:58:45.683+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:45.684+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:45.684+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:45.684+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:47.684Z
2017-02-14T18:58:47.684+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:47.685+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:47.685+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:47.685+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:49.685Z
2017-02-14T18:58:49.685+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:49.686+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:49.686+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:49.686+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:51.686Z
2017-02-14T18:58:50.135+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.6, filling with zeroes...
2017-02-14T18:58:50.137+0000 I STORAGE  [FileAllocator] FileAllocator: posix_fallocate failed: errno:28 No space left on device falling back
2017-02-14T18:58:50.139+0000 I STORAGE  [FileAllocator] error: failed to allocate new file: /var/lib/mongodb/boulderbrands_production.6 size: 2146435072 failure creating new datafile; lseek failed for fd 31 with errno: errno:2 No such file or directory.  will try again in 10 seconds
2017-02-14T18:58:50.139+0000 I -        [rsSync] Assertion: 12520:new file allocation failure
2017-02-14T18:58:50.146+0000 I NETWORK  [rsSync] trying reconnect to 1e-26:27017 (10.45.51.252) failed
2017-02-14T18:58:50.147+0000 I NETWORK  [rsSync] reconnect 1e-26:27017 (10.45.51.252) ok
2017-02-14T18:58:50.149+0000 E REPL     [rsSync] 12520 new file allocation failure
2017-02-14T18:58:50.149+0000 E REPL     [rsSync] initial sync attempt failed, 9 attempts remaining
2017-02-14T18:58:51.686+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:51.687+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:51.687+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:51.687+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:53.687Z
2017-02-14T18:58:53.687+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:53.688+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:53.688+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:53.688+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:55.688Z
2017-02-14T18:58:55.149+0000 I REPL     [rsSync] initial sync pending
2017-02-14T18:58:55.149+0000 I REPL     [ReplicationExecutor] syncing from: 1e-26:27017
2017-02-14T18:58:55.153+0000 I REPL     [rsSync] initial sync drop all databases
2017-02-14T18:58:55.154+0000 I STORAGE  [rsSync] dropAllDatabasesExceptLocal 4
2017-02-14T18:58:55.266+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T18:58:55.266+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T18:58:55.688+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:55.689+0000 I NETWORK  [conn40] end connection 10.45.51.252:57455 (0 connections now open)
2017-02-14T18:58:55.689+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57458 #41 (1 connection now open)
2017-02-14T18:58:55.690+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:55.690+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:55.690+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:57.690Z
2017-02-14T18:58:55.696+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T18:58:55.696+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T18:58:56.046+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T18:58:56.046+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T18:58:56.050+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T18:58:56.050+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T18:58:56.055+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T18:58:56.055+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T18:58:56.065+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T18:58:56.065+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T18:58:56.074+0000 I REPL     [rsSync] initial sync clone all databases
2017-02-14T18:58:56.079+0000 I REPL     [rsSync] initial sync cloning db: admin
2017-02-14T18:58:56.084+0000 I REPL     [rsSync] initial sync cloning db: aryzta_production
2017-02-14T18:58:56.088+0000 I INDEX    [rsSync] allocating new ns file /var/lib/mongodb/aryzta_production.ns, filling with zeroes...
2017-02-14T18:58:56.172+0000 I -        [rsSync] Assertion: 12520:new file allocation failure
2017-02-14T18:58:56.172+0000 W STORAGE  [rsSync] database /var/lib/mongodb aryzta_production could not be opened due to DBException 12520: new file allocation failure
2017-02-14T18:58:56.174+0000 E REPL     [rsSync] 12520 new file allocation failure
2017-02-14T18:58:56.174+0000 E REPL     [rsSync] initial sync attempt failed, 8 attempts remaining
2017-02-14T18:58:57.691+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:57.692+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:57.692+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:57.692+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:58:59.692Z
2017-02-14T18:58:59.692+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:58:59.693+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:58:59.693+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:58:59.693+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:01.693Z
2017-02-14T18:59:00.139+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.6, filling with zeroes...
2017-02-14T18:59:00.142+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.6, size: 2047MB,  took 0.002 secs
2017-02-14T18:59:01.174+0000 I REPL     [rsSync] initial sync pending
2017-02-14T18:59:01.175+0000 I REPL     [ReplicationExecutor] syncing from: 1e-26:27017
2017-02-14T18:59:01.179+0000 I REPL     [rsSync] initial sync drop all databases
2017-02-14T18:59:01.179+0000 I STORAGE  [rsSync] dropAllDatabasesExceptLocal 2
2017-02-14T18:59:01.179+0000 I STORAGE  [rsSync] database disappeared after listDatabases but before drop: aryzta_production
2017-02-14T18:59:01.179+0000 I REPL     [rsSync] initial sync clone all databases
2017-02-14T18:59:01.185+0000 I REPL     [rsSync] initial sync cloning db: admin
2017-02-14T18:59:01.190+0000 I REPL     [rsSync] initial sync cloning db: aryzta_production
2017-02-14T18:59:01.194+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/aryzta_production.0, filling with zeroes...
2017-02-14T18:59:01.196+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/aryzta_production.0, size: 64MB,  took 0.001 secs
2017-02-14T18:59:01.271+0000 I INDEX    [rsSync] build index on: aryzta_production.access_logs properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.access_logs" }
2017-02-14T18:59:01.271+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.275+0000 I INDEX    [rsSync] build index done.  scanned 1818 total records. 0 secs
2017-02-14T18:59:01.275+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/aryzta_production.1, filling with zeroes...
2017-02-14T18:59:01.276+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/aryzta_production.1, size: 128MB,  took 0 secs
2017-02-14T18:59:01.277+0000 I INDEX    [rsSync] build index on: aryzta_production.events properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.events" }
2017-02-14T18:59:01.277+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.277+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:59:01.279+0000 I INDEX    [rsSync] build index on: aryzta_production.warehouser_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.warehouser_pings" }
2017-02-14T18:59:01.279+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.279+0000 I INDEX    [rsSync] build index done.  scanned 115 total records. 0 secs
2017-02-14T18:59:01.284+0000 I INDEX    [rsSync] build index on: aryzta_production.action_dispatch.session.mongo_mapper_store.sessions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.action_dispatch.session.mongo_mapper_store.sessions" }
2017-02-14T18:59:01.284+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.287+0000 I INDEX    [rsSync] build index done.  scanned 1465 total records. 0 secs
2017-02-14T18:59:01.288+0000 I INDEX    [rsSync] build index on: aryzta_production.users properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.users" }
2017-02-14T18:59:01.288+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.288+0000 I INDEX    [rsSync] build index done.  scanned 5 total records. 0 secs
2017-02-14T18:59:01.289+0000 I INDEX    [rsSync] build index on: aryzta_production.configurations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.configurations" }
2017-02-14T18:59:01.289+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.289+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:01.291+0000 I INDEX    [rsSync] build index on: aryzta_production.organizations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.organizations" }
2017-02-14T18:59:01.291+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.291+0000 I INDEX    [rsSync] build index done.  scanned 46 total records. 0 secs
2017-02-14T18:59:01.293+0000 I INDEX    [rsSync] build index on: aryzta_production.accounts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.accounts" }
2017-02-14T18:59:01.293+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.293+0000 I INDEX    [rsSync] build index done.  scanned 5 total records. 0 secs
2017-02-14T18:59:01.294+0000 I INDEX    [rsSync] build index on: aryzta_production.attachment_types properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.attachment_types" }
2017-02-14T18:59:01.294+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.294+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T18:59:01.295+0000 I INDEX    [rsSync] build index on: aryzta_production.investment_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.investment_categories" }
2017-02-14T18:59:01.295+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.295+0000 I INDEX    [rsSync] build index done.  scanned 5 total records. 0 secs
2017-02-14T18:59:01.297+0000 I INDEX    [rsSync] build index on: aryzta_production.investment_sizes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.investment_sizes" }
2017-02-14T18:59:01.297+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.297+0000 I INDEX    [rsSync] build index done.  scanned 5 total records. 0 secs
2017-02-14T18:59:01.298+0000 I INDEX    [rsSync] build index on: aryzta_production.field_audit.audit_records properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.field_audit.audit_records" }
2017-02-14T18:59:01.298+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.300+0000 I INDEX    [rsSync] build index done.  scanned 55 total records. 0 secs
2017-02-14T18:59:01.302+0000 I INDEX    [rsSync] build index on: aryzta_production.investments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.investments" }
2017-02-14T18:59:01.302+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.302+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T18:59:01.303+0000 I INDEX    [rsSync] build index on: aryzta_production.user_dimensions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.user_dimensions" }
2017-02-14T18:59:01.303+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.303+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:59:01.304+0000 I INDEX    [rsSync] build index on: aryzta_production.custom_fields properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.custom_fields" }
2017-02-14T18:59:01.304+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.304+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:59:01.306+0000 I INDEX    [rsSync] build index on: aryzta_production.approval_rounds properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.approval_rounds" }
2017-02-14T18:59:01.306+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.306+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:59:01.308+0000 I INDEX    [rsSync] build index on: aryzta_production.authorities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.authorities" }
2017-02-14T18:59:01.308+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.308+0000 I INDEX    [rsSync] build index done.  scanned 8 total records. 0 secs
2017-02-14T18:59:01.309+0000 I INDEX    [rsSync] build index on: aryzta_production.approval_routes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.approval_routes" }
2017-02-14T18:59:01.309+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.309+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T18:59:01.311+0000 I INDEX    [rsSync] build index on: aryzta_production.budgets properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.budgets" }
2017-02-14T18:59:01.311+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.311+0000 I INDEX    [rsSync] build index done.  scanned 40 total records. 0 secs
2017-02-14T18:59:01.340+0000 I INDEX    [rsSync] build index on: aryzta_production.data_cubes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.data_cubes" }
2017-02-14T18:59:01.340+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.342+0000 I INDEX    [rsSync] build index done.  scanned 1368 total records. 0 secs
2017-02-14T18:59:01.344+0000 I INDEX    [rsSync] build index on: aryzta_production.approvals properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.approvals" }
2017-02-14T18:59:01.344+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.344+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:59:01.345+0000 I INDEX    [rsSync] build index on: aryzta_production.activities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.activities" }
2017-02-14T18:59:01.345+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.345+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T18:59:01.347+0000 I INDEX    [rsSync] build index on: aryzta_production.comments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.comments" }
2017-02-14T18:59:01.347+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.347+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:01.348+0000 I INDEX    [rsSync] build index on: aryzta_production.forecasts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.forecasts" }
2017-02-14T18:59:01.348+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.348+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:59:01.349+0000 I INDEX    [rsSync] build index on: aryzta_production.warehouse_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.warehouse_pings" }
2017-02-14T18:59:01.349+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.349+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:59:01.350+0000 I INDEX    [rsSync] build index on: aryzta_production.shared_views properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.shared_views" }
2017-02-14T18:59:01.350+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.350+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:01.351+0000 I INDEX    [rsSync] build index on: aryzta_production.cost_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.cost_categories" }
2017-02-14T18:59:01.351+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.351+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:59:01.353+0000 I INDEX    [rsSync] build index on: aryzta_production.progress_reports properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.progress_reports" }
2017-02-14T18:59:01.353+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.353+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:59:01.354+0000 I INDEX    [rsSync] build index on: aryzta_production.attachments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.attachments" }
2017-02-14T18:59:01.354+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.354+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:59:01.355+0000 I INDEX    [rsSync] build index on: aryzta_production.progress properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.progress" }
2017-02-14T18:59:01.355+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.355+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T18:59:01.355+0000 I REPL     [rsSync] initial sync cloning db: axia_production
2017-02-14T18:59:01.359+0000 I INDEX    [rsSync] allocating new ns file /var/lib/mongodb/axia_production.ns, filling with zeroes...
2017-02-14T18:59:01.449+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/axia_production.0, filling with zeroes...
2017-02-14T18:59:01.450+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/axia_production.0, size: 64MB,  took 0 secs
2017-02-14T18:59:01.601+0000 I INDEX    [rsSync] build index on: axia_production.access_logs properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.access_logs" }
2017-02-14T18:59:01.601+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.608+0000 I INDEX    [rsSync] build index done.  scanned 2689 total records. 0 secs
2017-02-14T18:59:01.609+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/axia_production.1, filling with zeroes...
2017-02-14T18:59:01.610+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/axia_production.1, size: 128MB,  took 0.001 secs
2017-02-14T18:59:01.612+0000 I INDEX    [rsSync] build index on: axia_production.events properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.events" }
2017-02-14T18:59:01.612+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.612+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T18:59:01.614+0000 I INDEX    [rsSync] build index on: axia_production.warehouser_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.warehouser_pings" }
2017-02-14T18:59:01.614+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.615+0000 I INDEX    [rsSync] build index done.  scanned 115 total records. 0 secs
2017-02-14T18:59:01.635+0000 I INDEX    [rsSync] build index on: axia_production.action_dispatch.session.mongo_mapper_store.sessions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.action_dispatch.session.mongo_mapper_store.sessions" }
2017-02-14T18:59:01.635+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.645+0000 I INDEX    [rsSync] build index done.  scanned 6075 total records. 0 secs
2017-02-14T18:59:01.648+0000 I INDEX    [rsSync] build index on: axia_production.users properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.users" }
2017-02-14T18:59:01.648+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.648+0000 I INDEX    [rsSync] build index done.  scanned 7 total records. 0 secs
2017-02-14T18:59:01.649+0000 I INDEX    [rsSync] build index on: axia_production.configurations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.configurations" }
2017-02-14T18:59:01.649+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.649+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:01.651+0000 I INDEX    [rsSync] build index on: axia_production.organizations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.organizations" }
2017-02-14T18:59:01.651+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.651+0000 I INDEX    [rsSync] build index done.  scanned 17 total records. 0 secs
2017-02-14T18:59:01.652+0000 I INDEX    [rsSync] build index on: axia_production.investment_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.investment_categories" }
2017-02-14T18:59:01.652+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.652+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T18:59:01.657+0000 I INDEX    [rsSync] build index on: axia_production.investments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.investments" }
2017-02-14T18:59:01.657+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.657+0000 I INDEX    [rsSync] build index done.  scanned 7 total records. 0 secs
2017-02-14T18:59:01.668+0000 I INDEX    [rsSync] build index on: axia_production.field_audit.audit_records properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.field_audit.audit_records" }
2017-02-14T18:59:01.668+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.671+0000 I INDEX    [rsSync] build index done.  scanned 1510 total records. 0 secs
2017-02-14T18:59:01.672+0000 I INDEX    [rsSync] build index on: axia_production.user_dimensions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.user_dimensions" }
2017-02-14T18:59:01.672+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.672+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:59:01.674+0000 I INDEX    [rsSync] build index on: axia_production.custom_fields properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.custom_fields" }
2017-02-14T18:59:01.674+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.674+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:01.675+0000 I INDEX    [rsSync] build index on: axia_production.approval_rounds properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.approval_rounds" }
2017-02-14T18:59:01.675+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.675+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:59:01.676+0000 I INDEX    [rsSync] build index on: axia_production.authorities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.authorities" }
2017-02-14T18:59:01.676+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.677+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T18:59:01.678+0000 I INDEX    [rsSync] build index on: axia_production.approval_routes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.approval_routes" }
2017-02-14T18:59:01.678+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.678+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:59:01.680+0000 I INDEX    [rsSync] build index on: axia_production.budgets properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.budgets" }
2017-02-14T18:59:01.680+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.680+0000 I INDEX    [rsSync] build index done.  scanned 26 total records. 0 secs
2017-02-14T18:59:01.693+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:01.697+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:01.697+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:01.697+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:03.697Z
2017-02-14T18:59:01.848+0000 I INDEX    [rsSync] build index on: axia_production.data_cubes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.data_cubes" }
2017-02-14T18:59:01.848+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.870+0000 I INDEX    [rsSync] build index done.  scanned 4900 total records. 0 secs
2017-02-14T18:59:01.871+0000 I INDEX    [rsSync] build index on: axia_production.accounts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.accounts" }
2017-02-14T18:59:01.871+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.872+0000 I INDEX    [rsSync] build index done.  scanned 8 total records. 0 secs
2017-02-14T18:59:01.873+0000 I INDEX    [rsSync] build index on: axia_production.shared_views properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.shared_views" }
2017-02-14T18:59:01.873+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.873+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T18:59:01.875+0000 I INDEX    [rsSync] build index on: axia_production.approvals properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.approvals" }
2017-02-14T18:59:01.875+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.875+0000 I INDEX    [rsSync] build index done.  scanned 7 total records. 0 secs
2017-02-14T18:59:01.877+0000 I INDEX    [rsSync] build index on: axia_production.activities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.activities" }
2017-02-14T18:59:01.877+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.877+0000 I INDEX    [rsSync] build index done.  scanned 39 total records. 0 secs
2017-02-14T18:59:01.878+0000 I INDEX    [rsSync] build index on: axia_production.comments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.comments" }
2017-02-14T18:59:01.878+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.879+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:59:01.880+0000 I INDEX    [rsSync] build index on: axia_production.pdf_render_jobs properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.pdf_render_jobs" }
2017-02-14T18:59:01.880+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.880+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:59:01.881+0000 I INDEX    [rsSync] build index on: axia_production.access_nonces properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.access_nonces" }
2017-02-14T18:59:01.882+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.882+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:59:01.883+0000 I INDEX    [rsSync] build index on: axia_production.fs.files properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.fs.files" }
2017-02-14T18:59:01.883+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.883+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T18:59:01.953+0000 I INDEX    [rsSync] build index on: axia_production.fs.chunks properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.fs.chunks" }
2017-02-14T18:59:01.953+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.953+0000 I INDEX    [rsSync] build index done.  scanned 24 total records. 0 secs
2017-02-14T18:59:01.955+0000 I INDEX    [rsSync] build index on: axia_production.vendors properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.vendors" }
2017-02-14T18:59:01.955+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.955+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:01.958+0000 I INDEX    [rsSync] build index on: axia_production.attachment_types properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.attachment_types" }
2017-02-14T18:59:01.958+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.958+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T18:59:01.966+0000 I INDEX    [rsSync] build index on: axia_production.forecasts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.forecasts" }
2017-02-14T18:59:01.966+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.966+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T18:59:01.967+0000 I INDEX    [rsSync] build index on: axia_production.user_guides properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.user_guides" }
2017-02-14T18:59:01.967+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.967+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:01.968+0000 I INDEX    [rsSync] build index on: axia_production.cost_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.cost_categories" }
2017-02-14T18:59:01.968+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.968+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T18:59:01.969+0000 I INDEX    [rsSync] build index on: axia_production.attachments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.attachments" }
2017-02-14T18:59:01.969+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.969+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T18:59:01.971+0000 I INDEX    [rsSync] build index on: axia_production.warehouse_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.warehouse_pings" }
2017-02-14T18:59:01.971+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.971+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:59:01.972+0000 I INDEX    [rsSync] build index on: axia_production.payments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.payments" }
2017-02-14T18:59:01.972+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.972+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:01.973+0000 I INDEX    [rsSync] build index on: axia_production.timelines properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.timelines" }
2017-02-14T18:59:01.973+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.973+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:01.974+0000 I INDEX    [rsSync] build index on: axia_production.progress_reports properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.progress_reports" }
2017-02-14T18:59:01.974+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:01.974+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:59:01.974+0000 I REPL     [rsSync] initial sync cloning db: boulderbrands_production
2017-02-14T18:59:01.978+0000 I INDEX    [rsSync] allocating new ns file /var/lib/mongodb/boulderbrands_production.ns, filling with zeroes...
2017-02-14T18:59:02.077+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.0, filling with zeroes...
2017-02-14T18:59:02.078+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.0, size: 64MB,  took 0 secs
2017-02-14T18:59:02.088+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.1, filling with zeroes...
2017-02-14T18:59:02.089+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.1, size: 128MB,  took 0 secs
2017-02-14T18:59:02.094+0000 I INDEX    [rsSync] build index on: boulderbrands_production.events properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.events" }
2017-02-14T18:59:02.094+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.095+0000 I INDEX    [rsSync] build index done.  scanned 796 total records. 0 secs
2017-02-14T18:59:02.201+0000 I INDEX    [rsSync] build index on: boulderbrands_production.access_logs properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.access_logs" }
2017-02-14T18:59:02.201+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.216+0000 I INDEX    [rsSync] build index done.  scanned 5433 total records. 0 secs
2017-02-14T18:59:02.218+0000 I INDEX    [rsSync] build index on: boulderbrands_production.warehouser_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.warehouser_pings" }
2017-02-14T18:59:02.218+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.219+0000 I INDEX    [rsSync] build index done.  scanned 115 total records. 0 secs
2017-02-14T18:59:02.425+0000 I INDEX    [rsSync] build index on: boulderbrands_production.action_dispatch.session.mongo_mapper_store.sessions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.action_dispatch.session.mongo_mapper_store.sessions" }
2017-02-14T18:59:02.425+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.561+0000 I INDEX    [rsSync] build index done.  scanned 67286 total records. 0 secs
2017-02-14T18:59:02.565+0000 I INDEX    [rsSync] build index on: boulderbrands_production.users properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.users" }
2017-02-14T18:59:02.565+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.565+0000 I INDEX    [rsSync] build index done.  scanned 60 total records. 0 secs
2017-02-14T18:59:02.566+0000 I INDEX    [rsSync] build index on: boulderbrands_production.configurations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.configurations" }
2017-02-14T18:59:02.566+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.566+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:02.572+0000 I INDEX    [rsSync] build index on: boulderbrands_production.organizations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.organizations" }
2017-02-14T18:59:02.572+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.572+0000 I INDEX    [rsSync] build index done.  scanned 9 total records. 0 secs
2017-02-14T18:59:02.573+0000 I INDEX    [rsSync] build index on: boulderbrands_production.accounts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.accounts" }
2017-02-14T18:59:02.573+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.573+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T18:59:02.574+0000 I INDEX    [rsSync] build index on: boulderbrands_production.attachment_types properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.attachment_types" }
2017-02-14T18:59:02.574+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.574+0000 I INDEX    [rsSync] build index done.  scanned 7 total records. 0 secs
2017-02-14T18:59:02.576+0000 I INDEX    [rsSync] build index on: boulderbrands_production.user_guides properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.user_guides" }
2017-02-14T18:59:02.576+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.576+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:02.577+0000 I INDEX    [rsSync] build index on: boulderbrands_production.investment_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.investment_categories" }
2017-02-14T18:59:02.577+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.577+0000 I INDEX    [rsSync] build index done.  scanned 10 total records. 0 secs
2017-02-14T18:59:02.578+0000 I INDEX    [rsSync] build index on: boulderbrands_production.investment_sizes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.investment_sizes" }
2017-02-14T18:59:02.578+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.578+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T18:59:02.684+0000 I INDEX    [rsSync] build index on: boulderbrands_production.field_audit.audit_records properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.field_audit.audit_records" }
2017-02-14T18:59:02.684+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.702+0000 I INDEX    [rsSync] build index done.  scanned 9289 total records. 0 secs
2017-02-14T18:59:02.704+0000 I INDEX    [rsSync] build index on: boulderbrands_production.cost_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.cost_categories" }
2017-02-14T18:59:02.704+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.704+0000 I INDEX    [rsSync] build index done.  scanned 11 total records. 0 secs
2017-02-14T18:59:02.791+0000 I INDEX    [rsSync] build index on: boulderbrands_production.investments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.investments" }
2017-02-14T18:59:02.791+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.794+0000 I INDEX    [rsSync] build index done.  scanned 780 total records. 0 secs
2017-02-14T18:59:02.796+0000 I INDEX    [rsSync] build index on: boulderbrands_production.vendors properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.vendors" }
2017-02-14T18:59:02.796+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.796+0000 I INDEX    [rsSync] build index done.  scanned 95 total records. 0 secs
2017-02-14T18:59:02.797+0000 I INDEX    [rsSync] build index on: boulderbrands_production.approval_rounds properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.approval_rounds" }
2017-02-14T18:59:02.797+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.797+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:02.799+0000 I INDEX    [rsSync] build index on: boulderbrands_production.authorities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.authorities" }
2017-02-14T18:59:02.799+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.799+0000 I INDEX    [rsSync] build index done.  scanned 11 total records. 0 secs
2017-02-14T18:59:02.800+0000 I INDEX    [rsSync] build index on: boulderbrands_production.approval_routes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.approval_routes" }
2017-02-14T18:59:02.800+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.800+0000 I INDEX    [rsSync] build index done.  scanned 8 total records. 0 secs
2017-02-14T18:59:02.827+0000 I INDEX    [rsSync] build index on: boulderbrands_production.approvals properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.approvals" }
2017-02-14T18:59:02.827+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.833+0000 I INDEX    [rsSync] build index done.  scanned 3483 total records. 0 secs
2017-02-14T18:59:02.896+0000 I INDEX    [rsSync] build index on: boulderbrands_production.activities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.activities" }
2017-02-14T18:59:02.896+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:02.918+0000 I INDEX    [rsSync] build index done.  scanned 8558 total records. 0 secs
2017-02-14T18:59:03.020+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.2, filling with zeroes...
2017-02-14T18:59:03.021+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.2, size: 256MB,  took 0.001 secs
2017-02-14T18:59:03.697+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:03.700+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:03.700+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:03.700+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:05.700Z
2017-02-14T18:59:04.700+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.3, filling with zeroes...
2017-02-14T18:59:04.701+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.3, size: 512MB,  took 0.001 secs
2017-02-14T18:59:05.700+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:05.708+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:05.708+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:05.708+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:07.708Z
2017-02-14T18:59:07.708+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:07.709+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:07.709+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:07.709+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:09.709Z
2017-02-14T18:59:09.305+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.4, filling with zeroes...
2017-02-14T18:59:09.307+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.4, size: 1024MB,  took 0.002 secs
2017-02-14T18:59:09.709+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:09.721+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:09.721+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:09.721+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:11.721Z
2017-02-14T18:59:11.721+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:11.730+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:11.730+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:11.730+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:13.730Z
2017-02-14T18:59:13.730+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:13.731+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:13.731+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:13.731+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:15.731Z
2017-02-14T18:59:15.732+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:15.737+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:15.737+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:15.737+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:17.737Z
2017-02-14T18:59:17.737+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:17.738+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:17.738+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:17.738+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:19.738Z
2017-02-14T18:59:19.738+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:19.739+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:19.739+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:19.739+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:21.739Z
2017-02-14T18:59:20.762+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.5, filling with zeroes...
2017-02-14T18:59:20.764+0000 I STORAGE  [FileAllocator] FileAllocator: posix_fallocate failed: errno:28 No space left on device falling back
2017-02-14T18:59:20.764+0000 I STORAGE  [FileAllocator] error: failed to allocate new file: /var/lib/mongodb/boulderbrands_production.5 size: 2146435072 failure creating new datafile; lseek failed for fd 30 with errno: errno:2 No such file or directory.  will try again in 10 seconds
2017-02-14T18:59:20.764+0000 I -        [rsSync] Assertion: 12520:new file allocation failure
2017-02-14T18:59:20.765+0000 I NETWORK  [rsSync] trying reconnect to 1e-26:27017 (10.45.51.252) failed
2017-02-14T18:59:20.767+0000 I NETWORK  [rsSync] reconnect 1e-26:27017 (10.45.51.252) ok
2017-02-14T18:59:20.770+0000 E REPL     [rsSync] 12520 new file allocation failure
2017-02-14T18:59:20.770+0000 E REPL     [rsSync] initial sync attempt failed, 7 attempts remaining
2017-02-14T18:59:21.740+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:21.741+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:21.741+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:21.741+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:23.741Z
2017-02-14T18:59:23.741+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:23.742+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:23.742+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:23.742+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:25.742Z
2017-02-14T18:59:25.732+0000 I NETWORK  [conn41] end connection 10.45.51.252:57458 (0 connections now open)
2017-02-14T18:59:25.733+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57462 #42 (1 connection now open)
2017-02-14T18:59:25.742+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:25.743+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:25.743+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:25.743+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:27.743Z
2017-02-14T18:59:25.770+0000 I REPL     [rsSync] initial sync pending
2017-02-14T18:59:25.770+0000 I REPL     [ReplicationExecutor] syncing from: 1e-26:27017
2017-02-14T18:59:25.774+0000 I REPL     [rsSync] initial sync drop all databases
2017-02-14T18:59:25.774+0000 I STORAGE  [rsSync] dropAllDatabasesExceptLocal 4
2017-02-14T18:59:26.103+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T18:59:26.103+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T18:59:26.364+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T18:59:26.364+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T18:59:26.567+0000 I STORAGE  [rsSync]   _applyOpToDataFiles() warning: extra == 9
2017-02-14T18:59:26.568+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T18:59:26.568+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T18:59:26.572+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T18:59:26.572+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T18:59:26.578+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T18:59:26.578+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T18:59:26.588+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T18:59:26.588+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T18:59:26.597+0000 I REPL     [rsSync] initial sync clone all databases
2017-02-14T18:59:26.603+0000 I REPL     [rsSync] initial sync cloning db: admin
2017-02-14T18:59:26.608+0000 I REPL     [rsSync] initial sync cloning db: aryzta_production
2017-02-14T18:59:26.611+0000 I INDEX    [rsSync] allocating new ns file /var/lib/mongodb/aryzta_production.ns, filling with zeroes...
2017-02-14T18:59:26.686+0000 I -        [rsSync] Assertion: 12520:new file allocation failure
2017-02-14T18:59:26.686+0000 W STORAGE  [rsSync] database /var/lib/mongodb aryzta_production could not be opened due to DBException 12520: new file allocation failure
2017-02-14T18:59:26.688+0000 E REPL     [rsSync] 12520 new file allocation failure
2017-02-14T18:59:26.688+0000 E REPL     [rsSync] initial sync attempt failed, 6 attempts remaining
2017-02-14T18:59:27.743+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:27.744+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:27.744+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:27.744+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:29.744Z
2017-02-14T18:59:29.744+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:29.745+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:29.746+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:29.746+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:31.746Z
2017-02-14T18:59:30.764+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.5, filling with zeroes...
2017-02-14T18:59:30.768+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.5, size: 2047MB,  took 0.004 secs
2017-02-14T18:59:31.688+0000 I REPL     [rsSync] initial sync pending
2017-02-14T18:59:31.688+0000 I REPL     [ReplicationExecutor] syncing from: 1e-26:27017
2017-02-14T18:59:31.693+0000 I REPL     [rsSync] initial sync drop all databases
2017-02-14T18:59:31.693+0000 I STORAGE  [rsSync] dropAllDatabasesExceptLocal 2
2017-02-14T18:59:31.693+0000 I STORAGE  [rsSync] database disappeared after listDatabases but before drop: aryzta_production
2017-02-14T18:59:31.693+0000 I REPL     [rsSync] initial sync clone all databases
2017-02-14T18:59:31.699+0000 I REPL     [rsSync] initial sync cloning db: admin
2017-02-14T18:59:31.703+0000 I REPL     [rsSync] initial sync cloning db: aryzta_production
2017-02-14T18:59:31.707+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/aryzta_production.0, filling with zeroes...
2017-02-14T18:59:31.708+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/aryzta_production.0, size: 64MB,  took 0.001 secs
2017-02-14T18:59:31.747+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:31.748+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:31.748+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:31.748+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:33.748Z
2017-02-14T18:59:31.880+0000 I INDEX    [rsSync] build index on: aryzta_production.access_logs properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.access_logs" }
2017-02-14T18:59:31.880+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.883+0000 I INDEX    [rsSync] build index done.  scanned 1818 total records. 0 secs
2017-02-14T18:59:31.883+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/aryzta_production.1, filling with zeroes...
2017-02-14T18:59:31.884+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/aryzta_production.1, size: 128MB,  took 0 secs
2017-02-14T18:59:31.886+0000 I INDEX    [rsSync] build index on: aryzta_production.events properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.events" }
2017-02-14T18:59:31.886+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.886+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:59:31.887+0000 I INDEX    [rsSync] build index on: aryzta_production.warehouser_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.warehouser_pings" }
2017-02-14T18:59:31.887+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.888+0000 I INDEX    [rsSync] build index done.  scanned 115 total records. 0 secs
2017-02-14T18:59:31.893+0000 I INDEX    [rsSync] build index on: aryzta_production.action_dispatch.session.mongo_mapper_store.sessions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.action_dispatch.session.mongo_mapper_store.sessions" }
2017-02-14T18:59:31.893+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.895+0000 I INDEX    [rsSync] build index done.  scanned 1465 total records. 0 secs
2017-02-14T18:59:31.896+0000 I INDEX    [rsSync] build index on: aryzta_production.users properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.users" }
2017-02-14T18:59:31.896+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.897+0000 I INDEX    [rsSync] build index done.  scanned 5 total records. 0 secs
2017-02-14T18:59:31.898+0000 I INDEX    [rsSync] build index on: aryzta_production.configurations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.configurations" }
2017-02-14T18:59:31.898+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.898+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:31.899+0000 I INDEX    [rsSync] build index on: aryzta_production.organizations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.organizations" }
2017-02-14T18:59:31.899+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.899+0000 I INDEX    [rsSync] build index done.  scanned 46 total records. 0 secs
2017-02-14T18:59:31.900+0000 I INDEX    [rsSync] build index on: aryzta_production.accounts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.accounts" }
2017-02-14T18:59:31.900+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.900+0000 I INDEX    [rsSync] build index done.  scanned 5 total records. 0 secs
2017-02-14T18:59:31.902+0000 I INDEX    [rsSync] build index on: aryzta_production.attachment_types properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.attachment_types" }
2017-02-14T18:59:31.902+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.902+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T18:59:31.903+0000 I INDEX    [rsSync] build index on: aryzta_production.investment_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.investment_categories" }
2017-02-14T18:59:31.903+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.903+0000 I INDEX    [rsSync] build index done.  scanned 5 total records. 0 secs
2017-02-14T18:59:31.904+0000 I INDEX    [rsSync] build index on: aryzta_production.investment_sizes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.investment_sizes" }
2017-02-14T18:59:31.904+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.904+0000 I INDEX    [rsSync] build index done.  scanned 5 total records. 0 secs
2017-02-14T18:59:31.905+0000 I INDEX    [rsSync] build index on: aryzta_production.field_audit.audit_records properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.field_audit.audit_records" }
2017-02-14T18:59:31.905+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.906+0000 I INDEX    [rsSync] build index done.  scanned 55 total records. 0 secs
2017-02-14T18:59:31.907+0000 I INDEX    [rsSync] build index on: aryzta_production.investments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.investments" }
2017-02-14T18:59:31.907+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.907+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T18:59:31.908+0000 I INDEX    [rsSync] build index on: aryzta_production.user_dimensions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.user_dimensions" }
2017-02-14T18:59:31.908+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.908+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:59:31.909+0000 I INDEX    [rsSync] build index on: aryzta_production.custom_fields properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.custom_fields" }
2017-02-14T18:59:31.909+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.909+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:59:31.910+0000 I INDEX    [rsSync] build index on: aryzta_production.approval_rounds properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.approval_rounds" }
2017-02-14T18:59:31.910+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.911+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:59:31.912+0000 I INDEX    [rsSync] build index on: aryzta_production.authorities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.authorities" }
2017-02-14T18:59:31.912+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.912+0000 I INDEX    [rsSync] build index done.  scanned 8 total records. 0 secs
2017-02-14T18:59:31.913+0000 I INDEX    [rsSync] build index on: aryzta_production.approval_routes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.approval_routes" }
2017-02-14T18:59:31.913+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.913+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T18:59:31.914+0000 I INDEX    [rsSync] build index on: aryzta_production.budgets properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.budgets" }
2017-02-14T18:59:31.914+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.915+0000 I INDEX    [rsSync] build index done.  scanned 40 total records. 0 secs
2017-02-14T18:59:31.962+0000 I INDEX    [rsSync] build index on: aryzta_production.data_cubes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.data_cubes" }
2017-02-14T18:59:31.962+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.965+0000 I INDEX    [rsSync] build index done.  scanned 1368 total records. 0 secs
2017-02-14T18:59:31.967+0000 I INDEX    [rsSync] build index on: aryzta_production.approvals properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.approvals" }
2017-02-14T18:59:31.967+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.967+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:59:31.968+0000 I INDEX    [rsSync] build index on: aryzta_production.activities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.activities" }
2017-02-14T18:59:31.968+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.968+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T18:59:31.970+0000 I INDEX    [rsSync] build index on: aryzta_production.comments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.comments" }
2017-02-14T18:59:31.970+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.970+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:31.971+0000 I INDEX    [rsSync] build index on: aryzta_production.forecasts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.forecasts" }
2017-02-14T18:59:31.971+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.971+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:59:31.973+0000 I INDEX    [rsSync] build index on: aryzta_production.warehouse_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.warehouse_pings" }
2017-02-14T18:59:31.973+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.973+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:59:31.975+0000 I INDEX    [rsSync] build index on: aryzta_production.shared_views properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.shared_views" }
2017-02-14T18:59:31.975+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.975+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:31.977+0000 I INDEX    [rsSync] build index on: aryzta_production.cost_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.cost_categories" }
2017-02-14T18:59:31.977+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.977+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:59:31.978+0000 I INDEX    [rsSync] build index on: aryzta_production.progress_reports properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.progress_reports" }
2017-02-14T18:59:31.978+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.978+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:59:31.979+0000 I INDEX    [rsSync] build index on: aryzta_production.attachments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.attachments" }
2017-02-14T18:59:31.979+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.979+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:59:31.981+0000 I INDEX    [rsSync] build index on: aryzta_production.progress properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.progress" }
2017-02-14T18:59:31.981+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:31.981+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T18:59:31.981+0000 I REPL     [rsSync] initial sync cloning db: axia_production
2017-02-14T18:59:31.985+0000 I INDEX    [rsSync] allocating new ns file /var/lib/mongodb/axia_production.ns, filling with zeroes...
2017-02-14T18:59:32.069+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/axia_production.0, filling with zeroes...
2017-02-14T18:59:32.070+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/axia_production.0, size: 64MB,  took 0 secs
2017-02-14T18:59:32.192+0000 I INDEX    [rsSync] build index on: axia_production.access_logs properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.access_logs" }
2017-02-14T18:59:32.192+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.200+0000 I INDEX    [rsSync] build index done.  scanned 2689 total records. 0 secs
2017-02-14T18:59:32.200+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/axia_production.1, filling with zeroes...
2017-02-14T18:59:32.201+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/axia_production.1, size: 128MB,  took 0 secs
2017-02-14T18:59:32.203+0000 I INDEX    [rsSync] build index on: axia_production.events properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.events" }
2017-02-14T18:59:32.203+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.203+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T18:59:32.204+0000 I INDEX    [rsSync] build index on: axia_production.warehouser_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.warehouser_pings" }
2017-02-14T18:59:32.204+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.205+0000 I INDEX    [rsSync] build index done.  scanned 115 total records. 0 secs
2017-02-14T18:59:32.226+0000 I INDEX    [rsSync] build index on: axia_production.action_dispatch.session.mongo_mapper_store.sessions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.action_dispatch.session.mongo_mapper_store.sessions" }
2017-02-14T18:59:32.227+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.237+0000 I INDEX    [rsSync] build index done.  scanned 6075 total records. 0 secs
2017-02-14T18:59:32.239+0000 I INDEX    [rsSync] build index on: axia_production.users properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.users" }
2017-02-14T18:59:32.239+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.239+0000 I INDEX    [rsSync] build index done.  scanned 7 total records. 0 secs
2017-02-14T18:59:32.240+0000 I INDEX    [rsSync] build index on: axia_production.configurations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.configurations" }
2017-02-14T18:59:32.240+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.240+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:32.241+0000 I INDEX    [rsSync] build index on: axia_production.organizations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.organizations" }
2017-02-14T18:59:32.241+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.242+0000 I INDEX    [rsSync] build index done.  scanned 17 total records. 0 secs
2017-02-14T18:59:32.243+0000 I INDEX    [rsSync] build index on: axia_production.investment_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.investment_categories" }
2017-02-14T18:59:32.243+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.243+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T18:59:32.247+0000 I INDEX    [rsSync] build index on: axia_production.investments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.investments" }
2017-02-14T18:59:32.247+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.247+0000 I INDEX    [rsSync] build index done.  scanned 7 total records. 0 secs
2017-02-14T18:59:32.257+0000 I INDEX    [rsSync] build index on: axia_production.field_audit.audit_records properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.field_audit.audit_records" }
2017-02-14T18:59:32.257+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.260+0000 I INDEX    [rsSync] build index done.  scanned 1510 total records. 0 secs
2017-02-14T18:59:32.261+0000 I INDEX    [rsSync] build index on: axia_production.user_dimensions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.user_dimensions" }
2017-02-14T18:59:32.261+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.261+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:59:32.262+0000 I INDEX    [rsSync] build index on: axia_production.custom_fields properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.custom_fields" }
2017-02-14T18:59:32.262+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.262+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:32.263+0000 I INDEX    [rsSync] build index on: axia_production.approval_rounds properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.approval_rounds" }
2017-02-14T18:59:32.263+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.263+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:59:32.264+0000 I INDEX    [rsSync] build index on: axia_production.authorities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.authorities" }
2017-02-14T18:59:32.264+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.264+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T18:59:32.266+0000 I INDEX    [rsSync] build index on: axia_production.approval_routes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.approval_routes" }
2017-02-14T18:59:32.266+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.266+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:59:32.267+0000 I INDEX    [rsSync] build index on: axia_production.budgets properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.budgets" }
2017-02-14T18:59:32.267+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.267+0000 I INDEX    [rsSync] build index done.  scanned 26 total records. 0 secs
2017-02-14T18:59:32.431+0000 I INDEX    [rsSync] build index on: axia_production.data_cubes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.data_cubes" }
2017-02-14T18:59:32.431+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.440+0000 I INDEX    [rsSync] build index done.  scanned 4900 total records. 0 secs
2017-02-14T18:59:32.441+0000 I INDEX    [rsSync] build index on: axia_production.accounts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.accounts" }
2017-02-14T18:59:32.441+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.441+0000 I INDEX    [rsSync] build index done.  scanned 8 total records. 0 secs
2017-02-14T18:59:32.442+0000 I INDEX    [rsSync] build index on: axia_production.shared_views properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.shared_views" }
2017-02-14T18:59:32.442+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.442+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T18:59:32.443+0000 I INDEX    [rsSync] build index on: axia_production.approvals properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.approvals" }
2017-02-14T18:59:32.443+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.444+0000 I INDEX    [rsSync] build index done.  scanned 7 total records. 0 secs
2017-02-14T18:59:32.445+0000 I INDEX    [rsSync] build index on: axia_production.activities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.activities" }
2017-02-14T18:59:32.445+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.445+0000 I INDEX    [rsSync] build index done.  scanned 39 total records. 0 secs
2017-02-14T18:59:32.446+0000 I INDEX    [rsSync] build index on: axia_production.comments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.comments" }
2017-02-14T18:59:32.446+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.446+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:59:32.447+0000 I INDEX    [rsSync] build index on: axia_production.pdf_render_jobs properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.pdf_render_jobs" }
2017-02-14T18:59:32.447+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.447+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T18:59:32.448+0000 I INDEX    [rsSync] build index on: axia_production.access_nonces properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.access_nonces" }
2017-02-14T18:59:32.448+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.448+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:59:32.450+0000 I INDEX    [rsSync] build index on: axia_production.fs.files properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.fs.files" }
2017-02-14T18:59:32.450+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.450+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T18:59:32.503+0000 I INDEX    [rsSync] build index on: axia_production.fs.chunks properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.fs.chunks" }
2017-02-14T18:59:32.503+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.503+0000 I INDEX    [rsSync] build index done.  scanned 24 total records. 0 secs
2017-02-14T18:59:32.505+0000 I INDEX    [rsSync] build index on: axia_production.vendors properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.vendors" }
2017-02-14T18:59:32.505+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.505+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:32.506+0000 I INDEX    [rsSync] build index on: axia_production.attachment_types properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.attachment_types" }
2017-02-14T18:59:32.506+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.506+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T18:59:32.507+0000 I INDEX    [rsSync] build index on: axia_production.forecasts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.forecasts" }
2017-02-14T18:59:32.507+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.508+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T18:59:32.509+0000 I INDEX    [rsSync] build index on: axia_production.user_guides properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.user_guides" }
2017-02-14T18:59:32.509+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.509+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:32.510+0000 I INDEX    [rsSync] build index on: axia_production.cost_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.cost_categories" }
2017-02-14T18:59:32.510+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.510+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T18:59:32.511+0000 I INDEX    [rsSync] build index on: axia_production.attachments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.attachments" }
2017-02-14T18:59:32.511+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.511+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T18:59:32.513+0000 I INDEX    [rsSync] build index on: axia_production.warehouse_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.warehouse_pings" }
2017-02-14T18:59:32.513+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.513+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:59:32.514+0000 I INDEX    [rsSync] build index on: axia_production.payments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.payments" }
2017-02-14T18:59:32.514+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.514+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:32.515+0000 I INDEX    [rsSync] build index on: axia_production.timelines properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.timelines" }
2017-02-14T18:59:32.515+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.515+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:32.516+0000 I INDEX    [rsSync] build index on: axia_production.progress_reports properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.progress_reports" }
2017-02-14T18:59:32.516+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.516+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T18:59:32.516+0000 I REPL     [rsSync] initial sync cloning db: boulderbrands_production
2017-02-14T18:59:32.520+0000 I INDEX    [rsSync] allocating new ns file /var/lib/mongodb/boulderbrands_production.ns, filling with zeroes...
2017-02-14T18:59:32.614+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.0, filling with zeroes...
2017-02-14T18:59:32.615+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.0, size: 64MB,  took 0 secs
2017-02-14T18:59:32.625+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.1, filling with zeroes...
2017-02-14T18:59:32.626+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.1, size: 128MB,  took 0 secs
2017-02-14T18:59:32.631+0000 I INDEX    [rsSync] build index on: boulderbrands_production.events properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.events" }
2017-02-14T18:59:32.631+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.633+0000 I INDEX    [rsSync] build index done.  scanned 796 total records. 0 secs
2017-02-14T18:59:32.738+0000 I INDEX    [rsSync] build index on: boulderbrands_production.access_logs properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.access_logs" }
2017-02-14T18:59:32.738+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.754+0000 I INDEX    [rsSync] build index done.  scanned 5433 total records. 0 secs
2017-02-14T18:59:32.756+0000 I INDEX    [rsSync] build index on: boulderbrands_production.warehouser_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.warehouser_pings" }
2017-02-14T18:59:32.756+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:32.756+0000 I INDEX    [rsSync] build index done.  scanned 115 total records. 0 secs
2017-02-14T18:59:32.952+0000 I INDEX    [rsSync] build index on: boulderbrands_production.action_dispatch.session.mongo_mapper_store.sessions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.action_dispatch.session.mongo_mapper_store.sessions" }
2017-02-14T18:59:32.953+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:33.109+0000 I INDEX    [rsSync] build index done.  scanned 67286 total records. 0 secs
2017-02-14T18:59:33.114+0000 I INDEX    [rsSync] build index on: boulderbrands_production.users properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.users" }
2017-02-14T18:59:33.114+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:33.114+0000 I INDEX    [rsSync] build index done.  scanned 60 total records. 0 secs
2017-02-14T18:59:33.116+0000 I INDEX    [rsSync] build index on: boulderbrands_production.configurations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.configurations" }
2017-02-14T18:59:33.116+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:33.116+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:33.118+0000 I INDEX    [rsSync] build index on: boulderbrands_production.organizations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.organizations" }
2017-02-14T18:59:33.118+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:33.118+0000 I INDEX    [rsSync] build index done.  scanned 9 total records. 0 secs
2017-02-14T18:59:33.119+0000 I INDEX    [rsSync] build index on: boulderbrands_production.accounts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.accounts" }
2017-02-14T18:59:33.119+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:33.119+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T18:59:33.121+0000 I INDEX    [rsSync] build index on: boulderbrands_production.attachment_types properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.attachment_types" }
2017-02-14T18:59:33.121+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:33.121+0000 I INDEX    [rsSync] build index done.  scanned 7 total records. 0 secs
2017-02-14T18:59:33.123+0000 I INDEX    [rsSync] build index on: boulderbrands_production.user_guides properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.user_guides" }
2017-02-14T18:59:33.123+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:33.123+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:33.125+0000 I INDEX    [rsSync] build index on: boulderbrands_production.investment_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.investment_categories" }
2017-02-14T18:59:33.125+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:33.125+0000 I INDEX    [rsSync] build index done.  scanned 10 total records. 0 secs
2017-02-14T18:59:33.127+0000 I INDEX    [rsSync] build index on: boulderbrands_production.investment_sizes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.investment_sizes" }
2017-02-14T18:59:33.127+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:33.127+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T18:59:33.189+0000 I INDEX    [rsSync] build index on: boulderbrands_production.field_audit.audit_records properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.field_audit.audit_records" }
2017-02-14T18:59:33.189+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:33.213+0000 I INDEX    [rsSync] build index done.  scanned 9289 total records. 0 secs
2017-02-14T18:59:33.215+0000 I INDEX    [rsSync] build index on: boulderbrands_production.cost_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.cost_categories" }
2017-02-14T18:59:33.215+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:33.215+0000 I INDEX    [rsSync] build index done.  scanned 11 total records. 0 secs
2017-02-14T18:59:33.296+0000 I INDEX    [rsSync] build index on: boulderbrands_production.investments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.investments" }
2017-02-14T18:59:33.296+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:33.299+0000 I INDEX    [rsSync] build index done.  scanned 780 total records. 0 secs
2017-02-14T18:59:33.303+0000 I INDEX    [rsSync] build index on: boulderbrands_production.vendors properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.vendors" }
2017-02-14T18:59:33.303+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:33.303+0000 I INDEX    [rsSync] build index done.  scanned 95 total records. 0 secs
2017-02-14T18:59:33.305+0000 I INDEX    [rsSync] build index on: boulderbrands_production.approval_rounds properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.approval_rounds" }
2017-02-14T18:59:33.305+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:33.305+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T18:59:33.306+0000 I INDEX    [rsSync] build index on: boulderbrands_production.authorities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.authorities" }
2017-02-14T18:59:33.306+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:33.306+0000 I INDEX    [rsSync] build index done.  scanned 11 total records. 0 secs
2017-02-14T18:59:33.308+0000 I INDEX    [rsSync] build index on: boulderbrands_production.approval_routes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.approval_routes" }
2017-02-14T18:59:33.308+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:33.308+0000 I INDEX    [rsSync] build index done.  scanned 8 total records. 0 secs
2017-02-14T18:59:33.333+0000 I INDEX    [rsSync] build index on: boulderbrands_production.approvals properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.approvals" }
2017-02-14T18:59:33.333+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:33.339+0000 I INDEX    [rsSync] build index done.  scanned 3483 total records. 0 secs
2017-02-14T18:59:33.401+0000 I INDEX    [rsSync] build index on: boulderbrands_production.activities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.activities" }
2017-02-14T18:59:33.401+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T18:59:33.422+0000 I INDEX    [rsSync] build index done.  scanned 8558 total records. 0 secs
2017-02-14T18:59:33.525+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.2, filling with zeroes...
2017-02-14T18:59:33.526+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.2, size: 256MB,  took 0 secs
2017-02-14T18:59:33.748+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:33.754+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:33.754+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:33.754+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:35.754Z
2017-02-14T18:59:35.187+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.3, filling with zeroes...
2017-02-14T18:59:35.190+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.3, size: 512MB,  took 0.002 secs
2017-02-14T18:59:35.754+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:35.755+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:35.755+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:35.755+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:37.755Z
2017-02-14T18:59:37.755+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:37.760+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:37.760+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:37.760+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:39.760Z
2017-02-14T18:59:39.760+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:39.764+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:39.764+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:39.764+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:41.764Z
2017-02-14T18:59:39.808+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.4, filling with zeroes...
2017-02-14T18:59:39.810+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.4, size: 1024MB,  took 0.001 secs
2017-02-14T18:59:41.765+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:41.771+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:41.771+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:41.771+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:43.771Z
2017-02-14T18:59:43.771+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:43.779+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:43.779+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:43.779+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:45.779Z
2017-02-14T18:59:45.779+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:45.787+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:45.787+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:45.787+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:47.787Z
2017-02-14T18:59:47.787+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:47.789+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:47.789+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:47.789+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:49.789Z
2017-02-14T18:59:49.789+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:49.795+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:49.795+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:49.795+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:51.795Z
2017-02-14T18:59:51.795+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:51.820+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:51.820+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:51.820+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:53.820Z
2017-02-14T18:59:53.820+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:53.821+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:53.821+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:53.821+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:55.821Z
2017-02-14T18:59:55.790+0000 I NETWORK  [conn42] end connection 10.45.51.252:57462 (0 connections now open)
2017-02-14T18:59:55.794+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57465 #43 (1 connection now open)
2017-02-14T18:59:55.821+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:55.825+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:55.825+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:55.825+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:57.825Z
2017-02-14T18:59:57.825+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:57.829+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:57.829+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:57.829+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T18:59:59.829Z
2017-02-14T18:59:59.829+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T18:59:59.831+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T18:59:59.831+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T18:59:59.831+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:01.831Z
2017-02-14T19:00:01.831+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:01.836+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:01.836+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:01.836+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:03.836Z
2017-02-14T19:00:03.836+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:03.840+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:03.841+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:03.841+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:05.840Z
2017-02-14T19:00:05.840+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:05.842+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:05.842+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:05.842+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:07.842Z
2017-02-14T19:00:07.842+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:07.843+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:07.843+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:07.843+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:09.843Z
2017-02-14T19:00:07.846+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.6, filling with zeroes...
2017-02-14T19:00:07.847+0000 I STORAGE  [FileAllocator] FileAllocator: posix_fallocate failed: errno:28 No space left on device falling back
2017-02-14T19:00:07.847+0000 I STORAGE  [FileAllocator] error: failed to allocate new file: /var/lib/mongodb/boulderbrands_production.6 size: 2146435072 failure creating new datafile; lseek failed for fd 31 with errno: errno:2 No such file or directory.  will try again in 10 seconds
2017-02-14T19:00:07.847+0000 I -        [rsSync] Assertion: 12520:new file allocation failure
2017-02-14T19:00:07.849+0000 I NETWORK  [rsSync] trying reconnect to 1e-26:27017 (10.45.51.252) failed
2017-02-14T19:00:07.850+0000 I NETWORK  [rsSync] reconnect 1e-26:27017 (10.45.51.252) ok
2017-02-14T19:00:07.852+0000 E REPL     [rsSync] 12520 new file allocation failure
2017-02-14T19:00:07.852+0000 E REPL     [rsSync] initial sync attempt failed, 5 attempts remaining
2017-02-14T19:00:09.844+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:09.845+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:09.845+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:09.845+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:11.845Z
2017-02-14T19:00:11.845+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:11.847+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:11.847+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:11.847+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:13.847Z
2017-02-14T19:00:12.852+0000 I REPL     [rsSync] initial sync pending
2017-02-14T19:00:12.861+0000 I REPL     [ReplicationExecutor] syncing from: 1e-26:27017
2017-02-14T19:00:12.866+0000 I REPL     [rsSync] initial sync drop all databases
2017-02-14T19:00:12.866+0000 I STORAGE  [rsSync] dropAllDatabasesExceptLocal 4
2017-02-14T19:00:13.847+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:13.848+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:13.848+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:13.848+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:15.848Z
2017-02-14T19:00:13.856+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T19:00:13.856+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T19:00:14.295+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T19:00:14.295+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T19:00:14.652+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T19:00:14.652+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T19:00:14.656+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T19:00:14.656+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T19:00:14.661+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T19:00:14.661+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T19:00:14.671+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T19:00:14.671+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T19:00:14.680+0000 I REPL     [rsSync] initial sync clone all databases
2017-02-14T19:00:14.686+0000 I REPL     [rsSync] initial sync cloning db: admin
2017-02-14T19:00:14.691+0000 I REPL     [rsSync] initial sync cloning db: aryzta_production
2017-02-14T19:00:14.694+0000 I INDEX    [rsSync] allocating new ns file /var/lib/mongodb/aryzta_production.ns, filling with zeroes...
2017-02-14T19:00:14.774+0000 I -        [rsSync] Assertion: 12520:new file allocation failure
2017-02-14T19:00:14.774+0000 W STORAGE  [rsSync] database /var/lib/mongodb aryzta_production could not be opened due to DBException 12520: new file allocation failure
2017-02-14T19:00:14.776+0000 E REPL     [rsSync] 12520 new file allocation failure
2017-02-14T19:00:14.776+0000 E REPL     [rsSync] initial sync attempt failed, 4 attempts remaining
2017-02-14T19:00:15.848+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:15.849+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:15.849+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:15.849+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:17.849Z
2017-02-14T19:00:17.848+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.6, filling with zeroes...
2017-02-14T19:00:17.849+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:17.850+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:17.851+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:17.851+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:19.850Z
2017-02-14T19:00:17.852+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.6, size: 2047MB,  took 0.003 secs
2017-02-14T19:00:19.776+0000 I REPL     [rsSync] initial sync pending
2017-02-14T19:00:19.776+0000 I REPL     [ReplicationExecutor] syncing from: 1e-26:27017
2017-02-14T19:00:19.781+0000 I REPL     [rsSync] initial sync drop all databases
2017-02-14T19:00:19.781+0000 I STORAGE  [rsSync] dropAllDatabasesExceptLocal 2
2017-02-14T19:00:19.781+0000 I STORAGE  [rsSync] database disappeared after listDatabases but before drop: aryzta_production
2017-02-14T19:00:19.781+0000 I REPL     [rsSync] initial sync clone all databases
2017-02-14T19:00:19.786+0000 I REPL     [rsSync] initial sync cloning db: admin
2017-02-14T19:00:19.791+0000 I REPL     [rsSync] initial sync cloning db: aryzta_production
2017-02-14T19:00:19.795+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/aryzta_production.0, filling with zeroes...
2017-02-14T19:00:19.797+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/aryzta_production.0, size: 64MB,  took 0.001 secs
2017-02-14T19:00:19.850+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:19.851+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:19.851+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:19.851+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:21.851Z
2017-02-14T19:00:19.871+0000 I INDEX    [rsSync] build index on: aryzta_production.access_logs properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.access_logs" }
2017-02-14T19:00:19.871+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.875+0000 I INDEX    [rsSync] build index done.  scanned 1818 total records. 0 secs
2017-02-14T19:00:19.875+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/aryzta_production.1, filling with zeroes...
2017-02-14T19:00:19.876+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/aryzta_production.1, size: 128MB,  took 0 secs
2017-02-14T19:00:19.877+0000 I INDEX    [rsSync] build index on: aryzta_production.events properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.events" }
2017-02-14T19:00:19.877+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.877+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T19:00:19.879+0000 I INDEX    [rsSync] build index on: aryzta_production.warehouser_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.warehouser_pings" }
2017-02-14T19:00:19.879+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.879+0000 I INDEX    [rsSync] build index done.  scanned 115 total records. 0 secs
2017-02-14T19:00:19.884+0000 I INDEX    [rsSync] build index on: aryzta_production.action_dispatch.session.mongo_mapper_store.sessions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.action_dispatch.session.mongo_mapper_store.sessions" }
2017-02-14T19:00:19.884+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.887+0000 I INDEX    [rsSync] build index done.  scanned 1465 total records. 0 secs
2017-02-14T19:00:19.888+0000 I INDEX    [rsSync] build index on: aryzta_production.users properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.users" }
2017-02-14T19:00:19.888+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.888+0000 I INDEX    [rsSync] build index done.  scanned 5 total records. 0 secs
2017-02-14T19:00:19.889+0000 I INDEX    [rsSync] build index on: aryzta_production.configurations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.configurations" }
2017-02-14T19:00:19.889+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.889+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:19.891+0000 I INDEX    [rsSync] build index on: aryzta_production.organizations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.organizations" }
2017-02-14T19:00:19.891+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.891+0000 I INDEX    [rsSync] build index done.  scanned 46 total records. 0 secs
2017-02-14T19:00:19.892+0000 I INDEX    [rsSync] build index on: aryzta_production.accounts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.accounts" }
2017-02-14T19:00:19.892+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.892+0000 I INDEX    [rsSync] build index done.  scanned 5 total records. 0 secs
2017-02-14T19:00:19.893+0000 I INDEX    [rsSync] build index on: aryzta_production.attachment_types properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.attachment_types" }
2017-02-14T19:00:19.893+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.893+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T19:00:19.894+0000 I INDEX    [rsSync] build index on: aryzta_production.investment_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.investment_categories" }
2017-02-14T19:00:19.894+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.894+0000 I INDEX    [rsSync] build index done.  scanned 5 total records. 0 secs
2017-02-14T19:00:19.895+0000 I INDEX    [rsSync] build index on: aryzta_production.investment_sizes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.investment_sizes" }
2017-02-14T19:00:19.895+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.895+0000 I INDEX    [rsSync] build index done.  scanned 5 total records. 0 secs
2017-02-14T19:00:19.897+0000 I INDEX    [rsSync] build index on: aryzta_production.field_audit.audit_records properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.field_audit.audit_records" }
2017-02-14T19:00:19.897+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.897+0000 I INDEX    [rsSync] build index done.  scanned 55 total records. 0 secs
2017-02-14T19:00:19.898+0000 I INDEX    [rsSync] build index on: aryzta_production.investments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.investments" }
2017-02-14T19:00:19.899+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.899+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T19:00:19.901+0000 I INDEX    [rsSync] build index on: aryzta_production.user_dimensions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.user_dimensions" }
2017-02-14T19:00:19.901+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.901+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T19:00:19.902+0000 I INDEX    [rsSync] build index on: aryzta_production.custom_fields properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.custom_fields" }
2017-02-14T19:00:19.902+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.902+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T19:00:19.903+0000 I INDEX    [rsSync] build index on: aryzta_production.approval_rounds properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.approval_rounds" }
2017-02-14T19:00:19.903+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.904+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T19:00:19.905+0000 I INDEX    [rsSync] build index on: aryzta_production.authorities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.authorities" }
2017-02-14T19:00:19.905+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.905+0000 I INDEX    [rsSync] build index done.  scanned 8 total records. 0 secs
2017-02-14T19:00:19.906+0000 I INDEX    [rsSync] build index on: aryzta_production.approval_routes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.approval_routes" }
2017-02-14T19:00:19.906+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.906+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T19:00:19.908+0000 I INDEX    [rsSync] build index on: aryzta_production.budgets properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.budgets" }
2017-02-14T19:00:19.908+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.908+0000 I INDEX    [rsSync] build index done.  scanned 40 total records. 0 secs
2017-02-14T19:00:19.938+0000 I INDEX    [rsSync] build index on: aryzta_production.data_cubes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.data_cubes" }
2017-02-14T19:00:19.938+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.940+0000 I INDEX    [rsSync] build index done.  scanned 1368 total records. 0 secs
2017-02-14T19:00:19.941+0000 I INDEX    [rsSync] build index on: aryzta_production.approvals properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.approvals" }
2017-02-14T19:00:19.941+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.941+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T19:00:19.942+0000 I INDEX    [rsSync] build index on: aryzta_production.activities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.activities" }
2017-02-14T19:00:19.942+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.942+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T19:00:19.943+0000 I INDEX    [rsSync] build index on: aryzta_production.comments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.comments" }
2017-02-14T19:00:19.943+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.943+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:19.945+0000 I INDEX    [rsSync] build index on: aryzta_production.forecasts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.forecasts" }
2017-02-14T19:00:19.945+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.945+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T19:00:19.946+0000 I INDEX    [rsSync] build index on: aryzta_production.warehouse_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.warehouse_pings" }
2017-02-14T19:00:19.946+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.946+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T19:00:19.947+0000 I INDEX    [rsSync] build index on: aryzta_production.shared_views properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.shared_views" }
2017-02-14T19:00:19.947+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.947+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:19.948+0000 I INDEX    [rsSync] build index on: aryzta_production.cost_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.cost_categories" }
2017-02-14T19:00:19.948+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.948+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T19:00:19.949+0000 I INDEX    [rsSync] build index on: aryzta_production.progress_reports properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.progress_reports" }
2017-02-14T19:00:19.949+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.949+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T19:00:19.950+0000 I INDEX    [rsSync] build index on: aryzta_production.attachments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.attachments" }
2017-02-14T19:00:19.950+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.950+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T19:00:19.951+0000 I INDEX    [rsSync] build index on: aryzta_production.progress properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.progress" }
2017-02-14T19:00:19.951+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:19.951+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T19:00:19.951+0000 I REPL     [rsSync] initial sync cloning db: axia_production
2017-02-14T19:00:19.955+0000 I INDEX    [rsSync] allocating new ns file /var/lib/mongodb/axia_production.ns, filling with zeroes...
2017-02-14T19:00:20.039+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/axia_production.0, filling with zeroes...
2017-02-14T19:00:20.040+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/axia_production.0, size: 64MB,  took 0 secs
2017-02-14T19:00:20.174+0000 I INDEX    [rsSync] build index on: axia_production.access_logs properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.access_logs" }
2017-02-14T19:00:20.174+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.179+0000 I INDEX    [rsSync] build index done.  scanned 2689 total records. 0 secs
2017-02-14T19:00:20.179+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/axia_production.1, filling with zeroes...
2017-02-14T19:00:20.180+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/axia_production.1, size: 128MB,  took 0 secs
2017-02-14T19:00:20.181+0000 I INDEX    [rsSync] build index on: axia_production.events properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.events" }
2017-02-14T19:00:20.181+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.181+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T19:00:20.195+0000 I INDEX    [rsSync] build index on: axia_production.warehouser_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.warehouser_pings" }
2017-02-14T19:00:20.195+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.195+0000 I INDEX    [rsSync] build index done.  scanned 115 total records. 0 secs
2017-02-14T19:00:20.214+0000 I INDEX    [rsSync] build index on: axia_production.action_dispatch.session.mongo_mapper_store.sessions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.action_dispatch.session.mongo_mapper_store.sessions" }
2017-02-14T19:00:20.214+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.225+0000 I INDEX    [rsSync] build index done.  scanned 6075 total records. 0 secs
2017-02-14T19:00:20.227+0000 I INDEX    [rsSync] build index on: axia_production.users properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.users" }
2017-02-14T19:00:20.227+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.227+0000 I INDEX    [rsSync] build index done.  scanned 7 total records. 0 secs
2017-02-14T19:00:20.228+0000 I INDEX    [rsSync] build index on: axia_production.configurations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.configurations" }
2017-02-14T19:00:20.228+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.228+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:20.229+0000 I INDEX    [rsSync] build index on: axia_production.organizations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.organizations" }
2017-02-14T19:00:20.229+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.229+0000 I INDEX    [rsSync] build index done.  scanned 17 total records. 0 secs
2017-02-14T19:00:20.230+0000 I INDEX    [rsSync] build index on: axia_production.investment_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.investment_categories" }
2017-02-14T19:00:20.231+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.231+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T19:00:20.234+0000 I INDEX    [rsSync] build index on: axia_production.investments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.investments" }
2017-02-14T19:00:20.234+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.235+0000 I INDEX    [rsSync] build index done.  scanned 7 total records. 0 secs
2017-02-14T19:00:20.245+0000 I INDEX    [rsSync] build index on: axia_production.field_audit.audit_records properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.field_audit.audit_records" }
2017-02-14T19:00:20.245+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.251+0000 I INDEX    [rsSync] build index done.  scanned 1510 total records. 0 secs
2017-02-14T19:00:20.252+0000 I INDEX    [rsSync] build index on: axia_production.user_dimensions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.user_dimensions" }
2017-02-14T19:00:20.252+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.252+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T19:00:20.254+0000 I INDEX    [rsSync] build index on: axia_production.custom_fields properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.custom_fields" }
2017-02-14T19:00:20.254+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.254+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:20.255+0000 I INDEX    [rsSync] build index on: axia_production.approval_rounds properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.approval_rounds" }
2017-02-14T19:00:20.255+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.255+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T19:00:20.256+0000 I INDEX    [rsSync] build index on: axia_production.authorities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.authorities" }
2017-02-14T19:00:20.256+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.256+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T19:00:20.257+0000 I INDEX    [rsSync] build index on: axia_production.approval_routes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.approval_routes" }
2017-02-14T19:00:20.258+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.258+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T19:00:20.259+0000 I INDEX    [rsSync] build index on: axia_production.budgets properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.budgets" }
2017-02-14T19:00:20.259+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.259+0000 I INDEX    [rsSync] build index done.  scanned 26 total records. 0 secs
2017-02-14T19:00:20.466+0000 I INDEX    [rsSync] build index on: axia_production.data_cubes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.data_cubes" }
2017-02-14T19:00:20.466+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.478+0000 I INDEX    [rsSync] build index done.  scanned 4900 total records. 0 secs
2017-02-14T19:00:20.480+0000 I INDEX    [rsSync] build index on: axia_production.accounts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.accounts" }
2017-02-14T19:00:20.480+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.480+0000 I INDEX    [rsSync] build index done.  scanned 8 total records. 0 secs
2017-02-14T19:00:20.482+0000 I INDEX    [rsSync] build index on: axia_production.shared_views properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.shared_views" }
2017-02-14T19:00:20.482+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.482+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T19:00:20.484+0000 I INDEX    [rsSync] build index on: axia_production.approvals properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.approvals" }
2017-02-14T19:00:20.484+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.484+0000 I INDEX    [rsSync] build index done.  scanned 7 total records. 0 secs
2017-02-14T19:00:20.487+0000 I INDEX    [rsSync] build index on: axia_production.activities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.activities" }
2017-02-14T19:00:20.487+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.487+0000 I INDEX    [rsSync] build index done.  scanned 39 total records. 0 secs
2017-02-14T19:00:20.488+0000 I INDEX    [rsSync] build index on: axia_production.comments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.comments" }
2017-02-14T19:00:20.488+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.489+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T19:00:20.492+0000 I INDEX    [rsSync] build index on: axia_production.pdf_render_jobs properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.pdf_render_jobs" }
2017-02-14T19:00:20.492+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.492+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T19:00:20.494+0000 I INDEX    [rsSync] build index on: axia_production.access_nonces properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.access_nonces" }
2017-02-14T19:00:20.494+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.494+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T19:00:20.496+0000 I INDEX    [rsSync] build index on: axia_production.fs.files properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.fs.files" }
2017-02-14T19:00:20.496+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.496+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T19:00:20.546+0000 I INDEX    [rsSync] build index on: axia_production.fs.chunks properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.fs.chunks" }
2017-02-14T19:00:20.546+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.546+0000 I INDEX    [rsSync] build index done.  scanned 24 total records. 0 secs
2017-02-14T19:00:20.547+0000 I INDEX    [rsSync] build index on: axia_production.vendors properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.vendors" }
2017-02-14T19:00:20.547+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.547+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:20.549+0000 I INDEX    [rsSync] build index on: axia_production.attachment_types properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.attachment_types" }
2017-02-14T19:00:20.549+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.549+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T19:00:20.550+0000 I INDEX    [rsSync] build index on: axia_production.forecasts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.forecasts" }
2017-02-14T19:00:20.550+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.550+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T19:00:20.551+0000 I INDEX    [rsSync] build index on: axia_production.user_guides properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.user_guides" }
2017-02-14T19:00:20.551+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.551+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:20.553+0000 I INDEX    [rsSync] build index on: axia_production.cost_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.cost_categories" }
2017-02-14T19:00:20.553+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.553+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T19:00:20.554+0000 I INDEX    [rsSync] build index on: axia_production.attachments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.attachments" }
2017-02-14T19:00:20.554+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.554+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T19:00:20.555+0000 I INDEX    [rsSync] build index on: axia_production.warehouse_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.warehouse_pings" }
2017-02-14T19:00:20.555+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.555+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T19:00:20.556+0000 I INDEX    [rsSync] build index on: axia_production.payments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.payments" }
2017-02-14T19:00:20.556+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.556+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:20.558+0000 I INDEX    [rsSync] build index on: axia_production.timelines properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.timelines" }
2017-02-14T19:00:20.558+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.558+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:20.559+0000 I INDEX    [rsSync] build index on: axia_production.progress_reports properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.progress_reports" }
2017-02-14T19:00:20.559+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.559+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T19:00:20.559+0000 I REPL     [rsSync] initial sync cloning db: boulderbrands_production
2017-02-14T19:00:20.563+0000 I INDEX    [rsSync] allocating new ns file /var/lib/mongodb/boulderbrands_production.ns, filling with zeroes...
2017-02-14T19:00:20.662+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.0, filling with zeroes...
2017-02-14T19:00:20.663+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.0, size: 64MB,  took 0 secs
2017-02-14T19:00:20.673+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.1, filling with zeroes...
2017-02-14T19:00:20.674+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.1, size: 128MB,  took 0.001 secs
2017-02-14T19:00:20.679+0000 I INDEX    [rsSync] build index on: boulderbrands_production.events properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.events" }
2017-02-14T19:00:20.679+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.681+0000 I INDEX    [rsSync] build index done.  scanned 796 total records. 0 secs
2017-02-14T19:00:20.797+0000 I INDEX    [rsSync] build index on: boulderbrands_production.access_logs properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.access_logs" }
2017-02-14T19:00:20.797+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.809+0000 I INDEX    [rsSync] build index done.  scanned 5433 total records. 0 secs
2017-02-14T19:00:20.811+0000 I INDEX    [rsSync] build index on: boulderbrands_production.warehouser_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.warehouser_pings" }
2017-02-14T19:00:20.811+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:20.811+0000 I INDEX    [rsSync] build index done.  scanned 115 total records. 0 secs
2017-02-14T19:00:21.029+0000 I INDEX    [rsSync] build index on: boulderbrands_production.action_dispatch.session.mongo_mapper_store.sessions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.action_dispatch.session.mongo_mapper_store.sessions" }
2017-02-14T19:00:21.029+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:21.162+0000 I INDEX    [rsSync] build index done.  scanned 67286 total records. 0 secs
2017-02-14T19:00:21.166+0000 I INDEX    [rsSync] build index on: boulderbrands_production.users properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.users" }
2017-02-14T19:00:21.166+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:21.166+0000 I INDEX    [rsSync] build index done.  scanned 60 total records. 0 secs
2017-02-14T19:00:21.167+0000 I INDEX    [rsSync] build index on: boulderbrands_production.configurations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.configurations" }
2017-02-14T19:00:21.167+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:21.167+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:21.168+0000 I INDEX    [rsSync] build index on: boulderbrands_production.organizations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.organizations" }
2017-02-14T19:00:21.168+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:21.169+0000 I INDEX    [rsSync] build index done.  scanned 9 total records. 0 secs
2017-02-14T19:00:21.170+0000 I INDEX    [rsSync] build index on: boulderbrands_production.accounts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.accounts" }
2017-02-14T19:00:21.170+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:21.170+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T19:00:21.171+0000 I INDEX    [rsSync] build index on: boulderbrands_production.attachment_types properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.attachment_types" }
2017-02-14T19:00:21.171+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:21.171+0000 I INDEX    [rsSync] build index done.  scanned 7 total records. 0 secs
2017-02-14T19:00:21.172+0000 I INDEX    [rsSync] build index on: boulderbrands_production.user_guides properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.user_guides" }
2017-02-14T19:00:21.172+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:21.172+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:21.174+0000 I INDEX    [rsSync] build index on: boulderbrands_production.investment_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.investment_categories" }
2017-02-14T19:00:21.174+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:21.174+0000 I INDEX    [rsSync] build index done.  scanned 10 total records. 0 secs
2017-02-14T19:00:21.175+0000 I INDEX    [rsSync] build index on: boulderbrands_production.investment_sizes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.investment_sizes" }
2017-02-14T19:00:21.175+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:21.175+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T19:00:21.239+0000 I INDEX    [rsSync] build index on: boulderbrands_production.field_audit.audit_records properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.field_audit.audit_records" }
2017-02-14T19:00:21.239+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:21.261+0000 I INDEX    [rsSync] build index done.  scanned 9289 total records. 0 secs
2017-02-14T19:00:21.263+0000 I INDEX    [rsSync] build index on: boulderbrands_production.cost_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.cost_categories" }
2017-02-14T19:00:21.263+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:21.263+0000 I INDEX    [rsSync] build index done.  scanned 11 total records. 0 secs
2017-02-14T19:00:21.342+0000 I INDEX    [rsSync] build index on: boulderbrands_production.investments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.investments" }
2017-02-14T19:00:21.342+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:21.345+0000 I INDEX    [rsSync] build index done.  scanned 780 total records. 0 secs
2017-02-14T19:00:21.347+0000 I INDEX    [rsSync] build index on: boulderbrands_production.vendors properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.vendors" }
2017-02-14T19:00:21.347+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:21.347+0000 I INDEX    [rsSync] build index done.  scanned 95 total records. 0 secs
2017-02-14T19:00:21.349+0000 I INDEX    [rsSync] build index on: boulderbrands_production.approval_rounds properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.approval_rounds" }
2017-02-14T19:00:21.349+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:21.349+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:21.350+0000 I INDEX    [rsSync] build index on: boulderbrands_production.authorities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.authorities" }
2017-02-14T19:00:21.350+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:21.350+0000 I INDEX    [rsSync] build index done.  scanned 11 total records. 0 secs
2017-02-14T19:00:21.351+0000 I INDEX    [rsSync] build index on: boulderbrands_production.approval_routes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.approval_routes" }
2017-02-14T19:00:21.351+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:21.351+0000 I INDEX    [rsSync] build index done.  scanned 8 total records. 0 secs
2017-02-14T19:00:21.376+0000 I INDEX    [rsSync] build index on: boulderbrands_production.approvals properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.approvals" }
2017-02-14T19:00:21.376+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:21.382+0000 I INDEX    [rsSync] build index done.  scanned 3483 total records. 0 secs
2017-02-14T19:00:21.471+0000 I INDEX    [rsSync] build index on: boulderbrands_production.activities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.activities" }
2017-02-14T19:00:21.471+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:21.487+0000 I INDEX    [rsSync] build index done.  scanned 8558 total records. 0 secs
2017-02-14T19:00:21.594+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.2, filling with zeroes...
2017-02-14T19:00:21.595+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.2, size: 256MB,  took 0.001 secs
2017-02-14T19:00:21.851+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:21.853+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:21.854+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:21.854+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:23.853Z
2017-02-14T19:00:23.360+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.3, filling with zeroes...
2017-02-14T19:00:23.362+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.3, size: 512MB,  took 0.001 secs
2017-02-14T19:00:23.853+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:23.856+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:23.856+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:23.856+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:25.856Z
2017-02-14T19:00:25.824+0000 I NETWORK  [conn43] end connection 10.45.51.252:57465 (0 connections now open)
2017-02-14T19:00:25.827+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57469 #44 (1 connection now open)
2017-02-14T19:00:25.857+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:25.859+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:25.859+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:25.859+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:27.859Z
2017-02-14T19:00:27.860+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:27.867+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:27.867+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:27.867+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:29.867Z
2017-02-14T19:00:27.873+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.4, filling with zeroes...
2017-02-14T19:00:27.942+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.4, size: 1024MB,  took 0.069 secs
2017-02-14T19:00:29.868+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:29.875+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:29.875+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:29.875+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:31.875Z
2017-02-14T19:00:31.876+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:31.881+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:31.881+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:31.881+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:33.881Z
2017-02-14T19:00:33.882+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:33.889+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:33.889+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:33.889+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:35.889Z
2017-02-14T19:00:35.889+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:35.890+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:35.890+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:35.890+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:37.890Z
2017-02-14T19:00:37.891+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:37.915+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:37.915+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:37.915+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:39.915Z
2017-02-14T19:00:39.303+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.5, filling with zeroes...
2017-02-14T19:00:39.304+0000 I STORAGE  [FileAllocator] FileAllocator: posix_fallocate failed: errno:28 No space left on device falling back
2017-02-14T19:00:39.304+0000 I STORAGE  [FileAllocator] error: failed to allocate new file: /var/lib/mongodb/boulderbrands_production.5 size: 2146435072 failure creating new datafile; lseek failed for fd 30 with errno: errno:2 No such file or directory.  will try again in 10 seconds
2017-02-14T19:00:39.304+0000 I -        [rsSync] Assertion: 12520:new file allocation failure
2017-02-14T19:00:39.306+0000 I NETWORK  [rsSync] trying reconnect to 1e-26:27017 (10.45.51.252) failed
2017-02-14T19:00:39.309+0000 I NETWORK  [rsSync] reconnect 1e-26:27017 (10.45.51.252) ok
2017-02-14T19:00:39.311+0000 E REPL     [rsSync] 12520 new file allocation failure
2017-02-14T19:00:39.311+0000 E REPL     [rsSync] initial sync attempt failed, 3 attempts remaining
2017-02-14T19:00:39.915+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:39.916+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:39.916+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:39.916+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:41.916Z
2017-02-14T19:00:41.916+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:41.918+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:41.918+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:41.918+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:43.918Z
2017-02-14T19:00:43.918+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:43.919+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:43.919+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:43.919+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:45.919Z
2017-02-14T19:00:44.311+0000 I REPL     [rsSync] initial sync pending
2017-02-14T19:00:44.312+0000 I REPL     [ReplicationExecutor] syncing from: 1e-26:27017
2017-02-14T19:00:44.316+0000 I REPL     [rsSync] initial sync drop all databases
2017-02-14T19:00:44.316+0000 I STORAGE  [rsSync] dropAllDatabasesExceptLocal 4
2017-02-14T19:00:44.320+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T19:00:44.320+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T19:00:44.582+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T19:00:44.582+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T19:00:44.787+0000 I STORAGE  [rsSync]   _applyOpToDataFiles() warning: extra == 9
2017-02-14T19:00:44.789+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T19:00:44.789+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T19:00:44.793+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T19:00:44.793+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T19:00:44.799+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T19:00:44.799+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T19:00:44.809+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T19:00:44.809+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T19:00:44.819+0000 I REPL     [rsSync] initial sync clone all databases
2017-02-14T19:00:44.824+0000 I REPL     [rsSync] initial sync cloning db: admin
2017-02-14T19:00:44.830+0000 I REPL     [rsSync] initial sync cloning db: aryzta_production
2017-02-14T19:00:44.833+0000 I INDEX    [rsSync] allocating new ns file /var/lib/mongodb/aryzta_production.ns, filling with zeroes...
2017-02-14T19:00:44.905+0000 I -        [rsSync] Assertion: 12520:new file allocation failure
2017-02-14T19:00:44.905+0000 W STORAGE  [rsSync] database /var/lib/mongodb aryzta_production could not be opened due to DBException 12520: new file allocation failure
2017-02-14T19:00:44.907+0000 E REPL     [rsSync] 12520 new file allocation failure
2017-02-14T19:00:44.907+0000 E REPL     [rsSync] initial sync attempt failed, 2 attempts remaining
2017-02-14T19:00:45.920+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:45.921+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:45.921+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:45.921+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:47.921Z
2017-02-14T19:00:47.921+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:47.922+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:47.922+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:47.922+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:49.922Z
2017-02-14T19:00:49.305+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.5, filling with zeroes...
2017-02-14T19:00:49.307+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.5, size: 2047MB,  took 0.002 secs
2017-02-14T19:00:49.907+0000 I REPL     [rsSync] initial sync pending
2017-02-14T19:00:49.908+0000 I REPL     [ReplicationExecutor] syncing from: 1e-26:27017
2017-02-14T19:00:49.912+0000 I REPL     [rsSync] initial sync drop all databases
2017-02-14T19:00:49.912+0000 I STORAGE  [rsSync] dropAllDatabasesExceptLocal 2
2017-02-14T19:00:49.912+0000 I STORAGE  [rsSync] database disappeared after listDatabases but before drop: aryzta_production
2017-02-14T19:00:49.912+0000 I REPL     [rsSync] initial sync clone all databases
2017-02-14T19:00:49.918+0000 I REPL     [rsSync] initial sync cloning db: admin
2017-02-14T19:00:49.922+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:49.922+0000 I REPL     [rsSync] initial sync cloning db: aryzta_production
2017-02-14T19:00:49.923+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:49.923+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:49.923+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:51.923Z
2017-02-14T19:00:49.926+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/aryzta_production.0, filling with zeroes...
2017-02-14T19:00:49.927+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/aryzta_production.0, size: 64MB,  took 0.001 secs
2017-02-14T19:00:50.003+0000 I INDEX    [rsSync] build index on: aryzta_production.access_logs properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.access_logs" }
2017-02-14T19:00:50.003+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.007+0000 I INDEX    [rsSync] build index done.  scanned 1818 total records. 0 secs
2017-02-14T19:00:50.007+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/aryzta_production.1, filling with zeroes...
2017-02-14T19:00:50.008+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/aryzta_production.1, size: 128MB,  took 0 secs
2017-02-14T19:00:50.009+0000 I INDEX    [rsSync] build index on: aryzta_production.events properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.events" }
2017-02-14T19:00:50.009+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.009+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T19:00:50.011+0000 I INDEX    [rsSync] build index on: aryzta_production.warehouser_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.warehouser_pings" }
2017-02-14T19:00:50.011+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.011+0000 I INDEX    [rsSync] build index done.  scanned 115 total records. 0 secs
2017-02-14T19:00:50.016+0000 I INDEX    [rsSync] build index on: aryzta_production.action_dispatch.session.mongo_mapper_store.sessions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.action_dispatch.session.mongo_mapper_store.sessions" }
2017-02-14T19:00:50.016+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.019+0000 I INDEX    [rsSync] build index done.  scanned 1465 total records. 0 secs
2017-02-14T19:00:50.020+0000 I INDEX    [rsSync] build index on: aryzta_production.users properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.users" }
2017-02-14T19:00:50.020+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.020+0000 I INDEX    [rsSync] build index done.  scanned 5 total records. 0 secs
2017-02-14T19:00:50.021+0000 I INDEX    [rsSync] build index on: aryzta_production.configurations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.configurations" }
2017-02-14T19:00:50.021+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.021+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:50.023+0000 I INDEX    [rsSync] build index on: aryzta_production.organizations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.organizations" }
2017-02-14T19:00:50.023+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.023+0000 I INDEX    [rsSync] build index done.  scanned 46 total records. 0 secs
2017-02-14T19:00:50.024+0000 I INDEX    [rsSync] build index on: aryzta_production.accounts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.accounts" }
2017-02-14T19:00:50.024+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.024+0000 I INDEX    [rsSync] build index done.  scanned 5 total records. 0 secs
2017-02-14T19:00:50.025+0000 I INDEX    [rsSync] build index on: aryzta_production.attachment_types properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.attachment_types" }
2017-02-14T19:00:50.025+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.025+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T19:00:50.026+0000 I INDEX    [rsSync] build index on: aryzta_production.investment_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.investment_categories" }
2017-02-14T19:00:50.026+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.026+0000 I INDEX    [rsSync] build index done.  scanned 5 total records. 0 secs
2017-02-14T19:00:50.028+0000 I INDEX    [rsSync] build index on: aryzta_production.investment_sizes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.investment_sizes" }
2017-02-14T19:00:50.028+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.028+0000 I INDEX    [rsSync] build index done.  scanned 5 total records. 0 secs
2017-02-14T19:00:50.029+0000 I INDEX    [rsSync] build index on: aryzta_production.field_audit.audit_records properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.field_audit.audit_records" }
2017-02-14T19:00:50.029+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.029+0000 I INDEX    [rsSync] build index done.  scanned 55 total records. 0 secs
2017-02-14T19:00:50.031+0000 I INDEX    [rsSync] build index on: aryzta_production.investments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.investments" }
2017-02-14T19:00:50.031+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.031+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T19:00:50.033+0000 I INDEX    [rsSync] build index on: aryzta_production.user_dimensions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.user_dimensions" }
2017-02-14T19:00:50.033+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.033+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T19:00:50.034+0000 I INDEX    [rsSync] build index on: aryzta_production.custom_fields properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.custom_fields" }
2017-02-14T19:00:50.034+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.034+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T19:00:50.035+0000 I INDEX    [rsSync] build index on: aryzta_production.approval_rounds properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.approval_rounds" }
2017-02-14T19:00:50.035+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.035+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T19:00:50.037+0000 I INDEX    [rsSync] build index on: aryzta_production.authorities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.authorities" }
2017-02-14T19:00:50.037+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.037+0000 I INDEX    [rsSync] build index done.  scanned 8 total records. 0 secs
2017-02-14T19:00:50.038+0000 I INDEX    [rsSync] build index on: aryzta_production.approval_routes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.approval_routes" }
2017-02-14T19:00:50.038+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.038+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T19:00:50.040+0000 I INDEX    [rsSync] build index on: aryzta_production.budgets properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.budgets" }
2017-02-14T19:00:50.040+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.040+0000 I INDEX    [rsSync] build index done.  scanned 40 total records. 0 secs
2017-02-14T19:00:50.069+0000 I INDEX    [rsSync] build index on: aryzta_production.data_cubes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.data_cubes" }
2017-02-14T19:00:50.069+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.072+0000 I INDEX    [rsSync] build index done.  scanned 1368 total records. 0 secs
2017-02-14T19:00:50.073+0000 I INDEX    [rsSync] build index on: aryzta_production.approvals properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.approvals" }
2017-02-14T19:00:50.073+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.073+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T19:00:50.074+0000 I INDEX    [rsSync] build index on: aryzta_production.activities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.activities" }
2017-02-14T19:00:50.074+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.074+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T19:00:50.075+0000 I INDEX    [rsSync] build index on: aryzta_production.comments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.comments" }
2017-02-14T19:00:50.075+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.075+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:50.076+0000 I INDEX    [rsSync] build index on: aryzta_production.forecasts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.forecasts" }
2017-02-14T19:00:50.076+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.076+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T19:00:50.078+0000 I INDEX    [rsSync] build index on: aryzta_production.warehouse_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.warehouse_pings" }
2017-02-14T19:00:50.078+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.078+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T19:00:50.079+0000 I INDEX    [rsSync] build index on: aryzta_production.shared_views properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.shared_views" }
2017-02-14T19:00:50.079+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.079+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:50.080+0000 I INDEX    [rsSync] build index on: aryzta_production.cost_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.cost_categories" }
2017-02-14T19:00:50.080+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.080+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T19:00:50.081+0000 I INDEX    [rsSync] build index on: aryzta_production.progress_reports properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.progress_reports" }
2017-02-14T19:00:50.081+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.081+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T19:00:50.082+0000 I INDEX    [rsSync] build index on: aryzta_production.attachments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.attachments" }
2017-02-14T19:00:50.082+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.082+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T19:00:50.083+0000 I INDEX    [rsSync] build index on: aryzta_production.progress properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "aryzta_production.progress" }
2017-02-14T19:00:50.083+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.083+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T19:00:50.083+0000 I REPL     [rsSync] initial sync cloning db: axia_production
2017-02-14T19:00:50.088+0000 I INDEX    [rsSync] allocating new ns file /var/lib/mongodb/axia_production.ns, filling with zeroes...
2017-02-14T19:00:50.176+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/axia_production.0, filling with zeroes...
2017-02-14T19:00:50.178+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/axia_production.0, size: 64MB,  took 0.001 secs
2017-02-14T19:00:50.320+0000 I INDEX    [rsSync] build index on: axia_production.access_logs properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.access_logs" }
2017-02-14T19:00:50.320+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.325+0000 I INDEX    [rsSync] build index done.  scanned 2689 total records. 0 secs
2017-02-14T19:00:50.325+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/axia_production.1, filling with zeroes...
2017-02-14T19:00:50.327+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/axia_production.1, size: 128MB,  took 0.001 secs
2017-02-14T19:00:50.328+0000 I INDEX    [rsSync] build index on: axia_production.events properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.events" }
2017-02-14T19:00:50.328+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.328+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T19:00:50.330+0000 I INDEX    [rsSync] build index on: axia_production.warehouser_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.warehouser_pings" }
2017-02-14T19:00:50.330+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.330+0000 I INDEX    [rsSync] build index done.  scanned 115 total records. 0 secs
2017-02-14T19:00:50.357+0000 I INDEX    [rsSync] build index on: axia_production.action_dispatch.session.mongo_mapper_store.sessions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.action_dispatch.session.mongo_mapper_store.sessions" }
2017-02-14T19:00:50.357+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.367+0000 I INDEX    [rsSync] build index done.  scanned 6075 total records. 0 secs
2017-02-14T19:00:50.369+0000 I INDEX    [rsSync] build index on: axia_production.users properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.users" }
2017-02-14T19:00:50.369+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.369+0000 I INDEX    [rsSync] build index done.  scanned 7 total records. 0 secs
2017-02-14T19:00:50.370+0000 I INDEX    [rsSync] build index on: axia_production.configurations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.configurations" }
2017-02-14T19:00:50.370+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.370+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:50.371+0000 I INDEX    [rsSync] build index on: axia_production.organizations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.organizations" }
2017-02-14T19:00:50.371+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.372+0000 I INDEX    [rsSync] build index done.  scanned 17 total records. 0 secs
2017-02-14T19:00:50.373+0000 I INDEX    [rsSync] build index on: axia_production.investment_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.investment_categories" }
2017-02-14T19:00:50.373+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.373+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T19:00:50.377+0000 I INDEX    [rsSync] build index on: axia_production.investments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.investments" }
2017-02-14T19:00:50.377+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.377+0000 I INDEX    [rsSync] build index done.  scanned 7 total records. 0 secs
2017-02-14T19:00:50.391+0000 I INDEX    [rsSync] build index on: axia_production.field_audit.audit_records properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.field_audit.audit_records" }
2017-02-14T19:00:50.391+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.396+0000 I INDEX    [rsSync] build index done.  scanned 1510 total records. 0 secs
2017-02-14T19:00:50.398+0000 I INDEX    [rsSync] build index on: axia_production.user_dimensions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.user_dimensions" }
2017-02-14T19:00:50.398+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.398+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T19:00:50.399+0000 I INDEX    [rsSync] build index on: axia_production.custom_fields properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.custom_fields" }
2017-02-14T19:00:50.399+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.399+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:50.400+0000 I INDEX    [rsSync] build index on: axia_production.approval_rounds properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.approval_rounds" }
2017-02-14T19:00:50.400+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.400+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T19:00:50.401+0000 I INDEX    [rsSync] build index on: axia_production.authorities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.authorities" }
2017-02-14T19:00:50.401+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.401+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T19:00:50.403+0000 I INDEX    [rsSync] build index on: axia_production.approval_routes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.approval_routes" }
2017-02-14T19:00:50.403+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.403+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T19:00:50.404+0000 I INDEX    [rsSync] build index on: axia_production.budgets properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.budgets" }
2017-02-14T19:00:50.404+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.404+0000 I INDEX    [rsSync] build index done.  scanned 26 total records. 0 secs
2017-02-14T19:00:50.565+0000 I INDEX    [rsSync] build index on: axia_production.data_cubes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.data_cubes" }
2017-02-14T19:00:50.566+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.575+0000 I INDEX    [rsSync] build index done.  scanned 4900 total records. 0 secs
2017-02-14T19:00:50.576+0000 I INDEX    [rsSync] build index on: axia_production.accounts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.accounts" }
2017-02-14T19:00:50.576+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.576+0000 I INDEX    [rsSync] build index done.  scanned 8 total records. 0 secs
2017-02-14T19:00:50.578+0000 I INDEX    [rsSync] build index on: axia_production.shared_views properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.shared_views" }
2017-02-14T19:00:50.578+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.578+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T19:00:50.579+0000 I INDEX    [rsSync] build index on: axia_production.approvals properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.approvals" }
2017-02-14T19:00:50.579+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.579+0000 I INDEX    [rsSync] build index done.  scanned 7 total records. 0 secs
2017-02-14T19:00:50.580+0000 I INDEX    [rsSync] build index on: axia_production.activities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.activities" }
2017-02-14T19:00:50.580+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.580+0000 I INDEX    [rsSync] build index done.  scanned 39 total records. 0 secs
2017-02-14T19:00:50.581+0000 I INDEX    [rsSync] build index on: axia_production.comments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.comments" }
2017-02-14T19:00:50.582+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.582+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T19:00:50.583+0000 I INDEX    [rsSync] build index on: axia_production.pdf_render_jobs properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.pdf_render_jobs" }
2017-02-14T19:00:50.583+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.583+0000 I INDEX    [rsSync] build index done.  scanned 2 total records. 0 secs
2017-02-14T19:00:50.584+0000 I INDEX    [rsSync] build index on: axia_production.access_nonces properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.access_nonces" }
2017-02-14T19:00:50.584+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.584+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T19:00:50.585+0000 I INDEX    [rsSync] build index on: axia_production.fs.files properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.fs.files" }
2017-02-14T19:00:50.585+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.585+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T19:00:50.635+0000 I INDEX    [rsSync] build index on: axia_production.fs.chunks properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.fs.chunks" }
2017-02-14T19:00:50.635+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.636+0000 I INDEX    [rsSync] build index done.  scanned 24 total records. 0 secs
2017-02-14T19:00:50.637+0000 I INDEX    [rsSync] build index on: axia_production.vendors properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.vendors" }
2017-02-14T19:00:50.637+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.637+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:50.638+0000 I INDEX    [rsSync] build index on: axia_production.attachment_types properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.attachment_types" }
2017-02-14T19:00:50.638+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.638+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T19:00:50.639+0000 I INDEX    [rsSync] build index on: axia_production.forecasts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.forecasts" }
2017-02-14T19:00:50.639+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.639+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T19:00:50.640+0000 I INDEX    [rsSync] build index on: axia_production.user_guides properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.user_guides" }
2017-02-14T19:00:50.640+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.640+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:50.641+0000 I INDEX    [rsSync] build index on: axia_production.cost_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.cost_categories" }
2017-02-14T19:00:50.642+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.642+0000 I INDEX    [rsSync] build index done.  scanned 3 total records. 0 secs
2017-02-14T19:00:50.643+0000 I INDEX    [rsSync] build index on: axia_production.attachments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.attachments" }
2017-02-14T19:00:50.643+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.643+0000 I INDEX    [rsSync] build index done.  scanned 4 total records. 0 secs
2017-02-14T19:00:50.644+0000 I INDEX    [rsSync] build index on: axia_production.warehouse_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.warehouse_pings" }
2017-02-14T19:00:50.644+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.644+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T19:00:50.645+0000 I INDEX    [rsSync] build index on: axia_production.payments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.payments" }
2017-02-14T19:00:50.645+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.645+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:50.646+0000 I INDEX    [rsSync] build index on: axia_production.timelines properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.timelines" }
2017-02-14T19:00:50.646+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.646+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:50.647+0000 I INDEX    [rsSync] build index on: axia_production.progress_reports properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "axia_production.progress_reports" }
2017-02-14T19:00:50.647+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.647+0000 I INDEX    [rsSync] build index done.  scanned 0 total records. 0 secs
2017-02-14T19:00:50.647+0000 I REPL     [rsSync] initial sync cloning db: boulderbrands_production
2017-02-14T19:00:50.651+0000 I INDEX    [rsSync] allocating new ns file /var/lib/mongodb/boulderbrands_production.ns, filling with zeroes...
2017-02-14T19:00:50.778+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.0, filling with zeroes...
2017-02-14T19:00:50.779+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.0, size: 64MB,  took 0.001 secs
2017-02-14T19:00:50.789+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.1, filling with zeroes...
2017-02-14T19:00:50.790+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.1, size: 128MB,  took 0 secs
2017-02-14T19:00:50.795+0000 I INDEX    [rsSync] build index on: boulderbrands_production.events properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.events" }
2017-02-14T19:00:50.795+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.796+0000 I INDEX    [rsSync] build index done.  scanned 796 total records. 0 secs
2017-02-14T19:00:50.904+0000 I INDEX    [rsSync] build index on: boulderbrands_production.access_logs properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.access_logs" }
2017-02-14T19:00:50.905+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.921+0000 I INDEX    [rsSync] build index done.  scanned 5433 total records. 0 secs
2017-02-14T19:00:50.923+0000 I INDEX    [rsSync] build index on: boulderbrands_production.warehouser_pings properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.warehouser_pings" }
2017-02-14T19:00:50.923+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:50.923+0000 I INDEX    [rsSync] build index done.  scanned 115 total records. 0 secs
2017-02-14T19:00:51.130+0000 I INDEX    [rsSync] build index on: boulderbrands_production.action_dispatch.session.mongo_mapper_store.sessions properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.action_dispatch.session.mongo_mapper_store.sessions" }
2017-02-14T19:00:51.130+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:51.268+0000 I INDEX    [rsSync] build index done.  scanned 67286 total records. 0 secs
2017-02-14T19:00:51.272+0000 I INDEX    [rsSync] build index on: boulderbrands_production.users properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.users" }
2017-02-14T19:00:51.272+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:51.272+0000 I INDEX    [rsSync] build index done.  scanned 60 total records. 0 secs
2017-02-14T19:00:51.273+0000 I INDEX    [rsSync] build index on: boulderbrands_production.configurations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.configurations" }
2017-02-14T19:00:51.273+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:51.273+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:51.275+0000 I INDEX    [rsSync] build index on: boulderbrands_production.organizations properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.organizations" }
2017-02-14T19:00:51.275+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:51.275+0000 I INDEX    [rsSync] build index done.  scanned 9 total records. 0 secs
2017-02-14T19:00:51.276+0000 I INDEX    [rsSync] build index on: boulderbrands_production.accounts properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.accounts" }
2017-02-14T19:00:51.276+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:51.276+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T19:00:51.277+0000 I INDEX    [rsSync] build index on: boulderbrands_production.attachment_types properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.attachment_types" }
2017-02-14T19:00:51.277+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:51.277+0000 I INDEX    [rsSync] build index done.  scanned 7 total records. 0 secs
2017-02-14T19:00:51.279+0000 I INDEX    [rsSync] build index on: boulderbrands_production.user_guides properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.user_guides" }
2017-02-14T19:00:51.279+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:51.279+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:51.280+0000 I INDEX    [rsSync] build index on: boulderbrands_production.investment_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.investment_categories" }
2017-02-14T19:00:51.280+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:51.280+0000 I INDEX    [rsSync] build index done.  scanned 10 total records. 0 secs
2017-02-14T19:00:51.281+0000 I INDEX    [rsSync] build index on: boulderbrands_production.investment_sizes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.investment_sizes" }
2017-02-14T19:00:51.281+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:51.281+0000 I INDEX    [rsSync] build index done.  scanned 6 total records. 0 secs
2017-02-14T19:00:51.343+0000 I INDEX    [rsSync] build index on: boulderbrands_production.field_audit.audit_records properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.field_audit.audit_records" }
2017-02-14T19:00:51.344+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:51.366+0000 I INDEX    [rsSync] build index done.  scanned 9289 total records. 0 secs
2017-02-14T19:00:51.368+0000 I INDEX    [rsSync] build index on: boulderbrands_production.cost_categories properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.cost_categories" }
2017-02-14T19:00:51.368+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:51.368+0000 I INDEX    [rsSync] build index done.  scanned 11 total records. 0 secs
2017-02-14T19:00:51.446+0000 I INDEX    [rsSync] build index on: boulderbrands_production.investments properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.investments" }
2017-02-14T19:00:51.446+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:51.449+0000 I INDEX    [rsSync] build index done.  scanned 780 total records. 0 secs
2017-02-14T19:00:51.451+0000 I INDEX    [rsSync] build index on: boulderbrands_production.vendors properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.vendors" }
2017-02-14T19:00:51.451+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:51.452+0000 I INDEX    [rsSync] build index done.  scanned 95 total records. 0 secs
2017-02-14T19:00:51.453+0000 I INDEX    [rsSync] build index on: boulderbrands_production.approval_rounds properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.approval_rounds" }
2017-02-14T19:00:51.453+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:51.453+0000 I INDEX    [rsSync] build index done.  scanned 1 total records. 0 secs
2017-02-14T19:00:51.454+0000 I INDEX    [rsSync] build index on: boulderbrands_production.authorities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.authorities" }
2017-02-14T19:00:51.454+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:51.454+0000 I INDEX    [rsSync] build index done.  scanned 11 total records. 0 secs
2017-02-14T19:00:51.456+0000 I INDEX    [rsSync] build index on: boulderbrands_production.approval_routes properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.approval_routes" }
2017-02-14T19:00:51.456+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:51.456+0000 I INDEX    [rsSync] build index done.  scanned 8 total records. 0 secs
2017-02-14T19:00:51.485+0000 I INDEX    [rsSync] build index on: boulderbrands_production.approvals properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.approvals" }
2017-02-14T19:00:51.485+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:51.491+0000 I INDEX    [rsSync] build index done.  scanned 3483 total records. 0 secs
2017-02-14T19:00:51.552+0000 I INDEX    [rsSync] build index on: boulderbrands_production.activities properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "boulderbrands_production.activities" }
2017-02-14T19:00:51.552+0000 I INDEX    [rsSync] 	 building index using bulk method
2017-02-14T19:00:51.575+0000 I INDEX    [rsSync] build index done.  scanned 8558 total records. 0 secs
2017-02-14T19:00:51.677+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.2, filling with zeroes...
2017-02-14T19:00:51.678+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.2, size: 256MB,  took 0.001 secs
2017-02-14T19:00:51.923+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:51.931+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:51.931+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:51.931+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:53.931Z
2017-02-14T19:00:53.420+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.3, filling with zeroes...
2017-02-14T19:00:53.422+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.3, size: 512MB,  took 0.001 secs
2017-02-14T19:00:53.931+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:53.932+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:53.932+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:53.932+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:55.932Z
2017-02-14T19:00:55.880+0000 I NETWORK  [conn44] end connection 10.45.51.252:57469 (0 connections now open)
2017-02-14T19:00:55.881+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57472 #45 (1 connection now open)
2017-02-14T19:00:55.932+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:55.933+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:55.934+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:55.934+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:57.934Z
2017-02-14T19:00:57.934+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:57.952+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:57.955+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:57.955+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:00:59.955Z
2017-02-14T19:00:58.389+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.4, filling with zeroes...
2017-02-14T19:00:58.532+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.4, size: 1024MB,  took 0.143 secs
2017-02-14T19:00:59.955+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:00:59.957+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:00:59.957+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:00:59.957+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:01:01.957Z
2017-02-14T19:01:01.958+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:01:01.960+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:01:01.960+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:01:01.960+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:01:03.960Z
2017-02-14T19:01:03.961+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:01:03.963+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:01:03.963+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:01:03.963+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:01:05.963Z
2017-02-14T19:01:05.963+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:01:05.965+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:01:05.965+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:01:05.965+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:01:07.965Z
2017-02-14T19:01:07.965+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:01:07.968+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:01:07.968+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:01:07.968+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:01:09.968Z
2017-02-14T19:01:09.968+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:01:09.970+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:01:09.970+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:01:09.970+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:01:11.970Z
2017-02-14T19:01:11.970+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:01:11.977+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:01:11.977+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:01:11.977+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:01:13.977Z
2017-02-14T19:01:13.977+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:01:13.981+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:01:13.981+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:01:13.981+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:01:15.981Z
2017-02-14T19:01:15.981+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:01:15.982+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:01:15.982+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:01:15.982+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:01:17.982Z
2017-02-14T19:01:17.982+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:01:17.986+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:01:17.986+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:01:17.986+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:01:19.986Z
2017-02-14T19:01:19.986+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:01:20.012+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:01:20.012+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:01:20.012+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:01:22.012Z
2017-02-14T19:01:22.012+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:01:22.013+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:01:22.013+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:01:22.013+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:01:24.013Z
2017-02-14T19:01:24.014+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:01:24.015+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:01:24.015+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:01:24.015+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:01:26.015Z
2017-02-14T19:01:25.915+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.6, filling with zeroes...
2017-02-14T19:01:25.917+0000 I STORAGE  [FileAllocator] FileAllocator: posix_fallocate failed: errno:28 No space left on device falling back
2017-02-14T19:01:25.917+0000 I STORAGE  [FileAllocator] error: failed to allocate new file: /var/lib/mongodb/boulderbrands_production.6 size: 2146435072 failure creating new datafile; lseek failed for fd 31 with errno: errno:2 No such file or directory.  will try again in 10 seconds
2017-02-14T19:01:25.917+0000 I -        [rsSync] Assertion: 12520:new file allocation failure
2017-02-14T19:01:25.918+0000 I NETWORK  [rsSync] trying reconnect to 1e-26:27017 (10.45.51.252) failed
2017-02-14T19:01:25.919+0000 I NETWORK  [rsSync] reconnect 1e-26:27017 (10.45.51.252) ok
2017-02-14T19:01:25.921+0000 E REPL     [rsSync] 12520 new file allocation failure
2017-02-14T19:01:25.921+0000 E REPL     [rsSync] initial sync attempt failed, 1 attempts remaining
2017-02-14T19:01:26.012+0000 I NETWORK  [conn45] end connection 10.45.51.252:57472 (0 connections now open)
2017-02-14T19:01:26.012+0000 I NETWORK  [initandlisten] connection accepted from 10.45.51.252:57476 #46 (1 connection now open)
2017-02-14T19:01:26.015+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:01:26.016+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:01:26.016+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:01:26.016+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:01:28.016Z
2017-02-14T19:01:28.016+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:01:28.017+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:01:28.017+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:01:28.017+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:01:30.017Z
2017-02-14T19:01:30.017+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:01:30.018+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:01:30.018+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:01:30.018+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:01:32.018Z
2017-02-14T19:01:30.921+0000 I REPL     [rsSync] initial sync pending
2017-02-14T19:01:30.922+0000 I REPL     [ReplicationExecutor] syncing from: 1e-26:27017
2017-02-14T19:01:30.926+0000 I REPL     [rsSync] initial sync drop all databases
2017-02-14T19:01:30.926+0000 I STORAGE  [rsSync] dropAllDatabasesExceptLocal 4
2017-02-14T19:01:31.886+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T19:01:31.886+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T19:01:32.018+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:01:32.019+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:01:32.019+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:01:32.019+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:01:34.019Z
2017-02-14T19:01:32.342+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T19:01:32.342+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T19:01:32.701+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T19:01:32.701+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T19:01:32.706+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T19:01:32.706+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T19:01:32.711+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T19:01:32.711+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T19:01:32.721+0000 I JOURNAL  [rsSync] journalCleanup...
2017-02-14T19:01:32.721+0000 I JOURNAL  [rsSync] removeJournalFiles
2017-02-14T19:01:32.731+0000 I REPL     [rsSync] initial sync clone all databases
2017-02-14T19:01:32.737+0000 I REPL     [rsSync] initial sync cloning db: admin
2017-02-14T19:01:32.741+0000 I REPL     [rsSync] initial sync cloning db: aryzta_production
2017-02-14T19:01:32.745+0000 I INDEX    [rsSync] allocating new ns file /var/lib/mongodb/aryzta_production.ns, filling with zeroes...
2017-02-14T19:01:32.825+0000 I -        [rsSync] Assertion: 12520:new file allocation failure
2017-02-14T19:01:32.825+0000 W STORAGE  [rsSync] database /var/lib/mongodb aryzta_production could not be opened due to DBException 12520: new file allocation failure
2017-02-14T19:01:32.827+0000 E REPL     [rsSync] 12520 new file allocation failure
2017-02-14T19:01:32.827+0000 E REPL     [rsSync] initial sync attempt failed, 0 attempts remaining
2017-02-14T19:01:34.020+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:01:34.021+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:01:34.021+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:01:34.021+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:01:36.021Z
2017-02-14T19:01:35.917+0000 I STORAGE  [FileAllocator] allocating new datafile /var/lib/mongodb/boulderbrands_production.6, filling with zeroes...
2017-02-14T19:01:35.921+0000 I STORAGE  [FileAllocator] done allocating datafile /var/lib/mongodb/boulderbrands_production.6, size: 2047MB,  took 0.004 secs
2017-02-14T19:01:36.021+0000 D REPL     [ReplicationExecutor] Scheduling replSetHeartbeat to 1e-26:27017
2017-02-14T19:01:36.022+0000 D REPL     [ReplExecNetThread-0] Network status of sending replSetHeartbeat to 1e-26:27017 was OK
2017-02-14T19:01:36.022+0000 D REPL     [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg:  
2017-02-14T19:01:36.022+0000 D REPL     [ReplicationExecutor] Scheduling heartbeat to 1e-26:27017 at 2017-02-14T19:01:38.022Z
2017-02-14T19:01:37.828+0000 F REPL     [rsSync] The maximum number of retries have been exhausted for initial sync.
2017-02-14T19:01:37.828+0000 I -        [rsSync] Fatal Assertion 16233
2017-02-14T19:01:37.829+0000 I -        [rsSync] 

***aborting after fassert() failure