[SERVER-27750] Sharding component LogicalTimeMetadata distribution Created: 19/Jan/17  Updated: 13/Jun/17  Resolved: 14/Mar/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.5.5

Type: Task Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-27749 Integrate LogicalTimeMetadata with me... Closed
depends on SERVER-27855 Attach all NetworkInterface instances... Closed
Duplicate
is duplicated by SERVER-27718 Implement Logical Time propagation logic Closed
Related
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-02-13, Sharding 2017-03-06, Sharding 2017-03-27
Participants:
Linked BF Score: 0

 Description   
  • Add LogicalTimeMetadata to legacy connection pools
  • Make sure mongos processes LogicalTimeMetadata from clients and also attaches them to responses


 Comments   
Comment by Githook User [ 13/Jun/17 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-27750 Remove unneeded comment

ReplicaSetMonitor-TaskExecutor doesn't need the LogicalTimeMetadataHook since it is not being used to send outgoing requests. The individual ReplicasSetMonitors uses connections from the globalConnectionPool to talk to the replica sets members.
Branch: master
https://github.com/mongodb/mongo/commit/fd26a441a06498183f1217fa06f32f86e4a5a372

Comment by Githook User [ 14/Mar/17 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-27750 Handle and include LogicalTime in mongos request/response
Branch: master
https://github.com/mongodb/mongo/commit/e1ce1ad010926fc5c67851b88a212b6f035f3e77

Comment by Githook User [ 10/Mar/17 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-27750 Always attach the configsvr metadata in ShardingEgress*Hooks
Branch: master
https://github.com/mongodb/mongo/commit/a8d1a9d89f374969266ffddee158fef03cdbf174

Comment by Githook User [ 10/Mar/17 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: Revert "Revert "SERVER-27750 Attach LogicalTimeMetadata to globalConnPool and shardConnectionPool""

This reverts commit 4e2cb91ed1fe8a9a8caead72a7f0bd56b2ba28d1.
Branch: master
https://github.com/mongodb/mongo/commit/a067d77c06242aed80ccbf9e6d03b6a054849ffa

Comment by Githook User [ 09/Mar/17 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: Revert "SERVER-27750 Attach LogicalTimeMetadata to globalConnPool and shardConnectionPool"

This reverts commit 34dbe2a42d1db621f16555878b57f48efb30cc28.
Branch: master
https://github.com/mongodb/mongo/commit/4e2cb91ed1fe8a9a8caead72a7f0bd56b2ba28d1

Comment by Githook User [ 08/Mar/17 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-27750 Attach LogicalTimeMetadata to globalConnPool and shardConnectionPool

This also include refactor work to cleanup ShardingEgressMetadataHook api and allow ShardingConnectionHook to take EgressMetadataHookList.
Branch: master
https://github.com/mongodb/mongo/commit/34dbe2a42d1db621f16555878b57f48efb30cc28

Generated at Thu Feb 08 04:16:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.