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

Merge downstream gh #225

Merged
merged 17 commits into from
Jul 11, 2016
Merged

Merge downstream gh #225

merged 17 commits into from
Jul 11, 2016

Conversation

shlomi-noach
Copy link
Contributor

expiring maintenance for dead nodes
  • database_instance_maintenance now indicates processing node hostname/token
  • active node expires entries when such hostname/token are not alive
  • excluding (not expiring) maintenance locks explicitly set by the user (begin=maintenance)

Storyline, closes #224

adjusting negative replication lag seconds

Storyline, closes #212

When negative replication lag is encountered, we emit a WARNING and adjust to 0. (previous behavior was to fail insertion)

displaying GTID sets in node modal

Only when GTID is enabled. Closes #216

HTTP can listen on unix-socket
  • Introducing ListenSocket config variable; when on-empty, http service listens on unix socket instead of TCP. It is the responsibility of the user to make sure the file does not exist beforehand.

Closes #222

Added NodeHealthExpiry config variable

By default true so as to be backwards compatible, this can be used to only expire node health on daemon services, as opposed to CLI invocations.

adding necessary index to node_health

This adds a required index for the node_health cleanup queries

Shlomi Noach added 17 commits June 20, 2016 14:12
adding necessary index to node_health
Added `NodeHealthExpiry` config variable
supporting which-cluster-gh-ost-slaves command
allowing gh-ost replicas to have replicas
- `database_instance_maintenance` now indicates processing node hostname/token
- active node expires entries when such hostname/token are not alive
- excluding (not expiring) maintenance locks explicitly set by the user (`begin=maintenance`)
expiring maintenance for dead nodes
displaying GTID sets in node modal
adjusting negative replication lag seconds
- Introducing `ListenSocket` config variable; when on-empty, `http` service listens on unix socket instead of `TCP`. It is the responsibility of the user to make sure the file does not exist beforehand.
HTTP can listen on unix-socket
Merge pull request #217 from outbrain/merge-downstream-gh
@shlomi-noach shlomi-noach merged commit 69145f2 into master Jul 11, 2016
@shlomi-noach shlomi-noach deleted the merge-downstream-gh branch July 11, 2016 09:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant