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.

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

Snapshot and API bind addresses #2274

Merged
merged 7 commits into from
Apr 13, 2015
Merged

Snapshot and API bind addresses #2274

merged 7 commits into from
Apr 13, 2015

Conversation

jwilder
Copy link
Contributor

@jwilder jwilder commented Apr 13, 2015

This PR does the following:

  • Moves all the data node handlers under a /data prefix to make the top-level handler less brittle.
  • Removes the separate snapshot listener and makes it an endpoint on the cluster server at /data/snapshot
  • Removes the [snapshot].bind-address and [snapshot].port config sections since it now uses the cluster bind address and port
  • Fixes the HTTP API listener so that it can actually be run on a separate interface and port from the cluster addr.

jwilder added 3 commits April 13, 2015 15:38
Move the data node specific routes under a common /data prefix so
add new handler does require updates to the top level handler as well.
log.Fatalf("snapshot server failed to listen on %s: %s", cmd.config.SnapshotAddr(), err)
}
log.Printf("snapshot server listening on %s", cmd.config.SnapshotAddr())
log.Printf("snaphot server listening on %s", cmd.config.ClusterAddr())
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

snaphot => snapshot

@otoolep
Copy link
Contributor

otoolep commented Apr 13, 2015

+1, nice to see that top-level URL routing fixed up.

@toddboom
Copy link
Contributor

One small typo in a log line, otherwise 👍

jwilder added 4 commits April 13, 2015 16:27
This removes the separate port listener and adds it as a route
on the cluster port.
Now listens on the cluster port.  Snapshots can still be disabled
though.
The HTTP bind address/port config was not actually being used.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants