Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remote shard mapping over TCP #3376

Merged
merged 2 commits into from
Jul 20, 2015
Merged

Remote shard mapping over TCP #3376

merged 2 commits into from
Jul 20, 2015

Commits on Jul 20, 2015

  1. RemoteShard mapping now performed over TCP 

    With this change remote mapping no longer uses HTTP, as the HTTP ports
exposed by nodes on the cluster are not known cluster wide. The TCP
ports exposed by the cluster service are, so this change uses that
functionality. Each RemoteMapper has its own dedicated connection pool
for each node, and remote mapping TCP connections are in no way coupled
with query TCP connections.
    @otoolep
    otoolep committed Jul 20, 2015
    Configuration menu
    Copy the full SHA
    425a65f View commit details
    Browse the repository at this point in the history

  2. Allow remote mapping to be forced 

    This is useful primarily for testing.
    @otoolep
    otoolep committed Jul 20, 2015
    Configuration menu
    Copy the full SHA
    10eecb4 View commit details
    Browse the repository at this point in the history