search

outbrain / orchestrator

MySQL replication topology manager/visualizer
Other
827 stars 168 forks source link

which-cluster-osc-slaves picks unsuitable slaves #107

Open dveeden opened 8 years ago

dveeden commented 8 years ago

The orchestrator -c which-cluster-osc-slaves can pick slaves which are:

It might also be nice to pick at least one slave on each branch of the replication tree. Also I would like to configure and/or specify the number of slaves I want.

shlomi-noach commented 8 years ago

Please explain "It might also be nice to pick at least one slave on each branch of the replication tree"

On Monday, September 14, 2015, Daniël van Eeden notifications@github.com wrote:

The orchestrator -c which-cluster-osc-slaves can pick slaves which are:

  • Delayed (OSC will wait until the table has reached all slaves...)
  • Have filters (See --check-replication-filters for pt-online-schema-change)

It might also be nice to pick at least one slave on each branch of the replication tree. Also I would like to configure and/or specify the number of slaves I want.

— Reply to this email directly or view it on GitHub https://github.com/outbrain/orchestrator/issues/107.

dveeden commented 8 years ago

If you have this:

      master
/      /      \     \       \
IM   IM    IM   IM     SSS
|      |       |     |
SS  SSS   SS    BLS
                        |
                        SSS

Then it should try to pick one slave of each group of leave slaves. E.g. always pick at lease one FRA4, AMS4 and LHR4 slave.

On 14/09/15 15:20, Shlomi Noach wrote:

Please explain "It might also be nice to pick at least one slave on each branch of the replication tree"

On Monday, September 14, 2015, Daniël van Eeden notifications@github.com wrote:

The orchestrator -c which-cluster-osc-slaves can pick slaves which are:

  • Delayed (OSC will wait until the table has reached all slaves...)
  • Have filters (See --check-replication-filters for pt-online-schema-change)

It might also be nice to pick at least one slave on each branch of the replication tree. Also I would like to configure and/or specify the number of slaves I want.

— Reply to this email directly or view it on GitHub https://github.com/outbrain/orchestrator/issues/107.

— Reply to this email directly or view it on GitHub https://github.com/outbrain/orchestrator/issues/107#issuecomment-140072102.

shlomi-noach commented 8 years ago

I will try to generalize this somehow, as this is but one particular case. Definitely I can easily pick slaves from all DCs.

On Monday, September 14, 2015, Daniël van Eeden notifications@github.com wrote:

If you have this:

master / / \ \ \ IM IM IM IM SSS SS SSS SS BLS

SSS

Then it should try to pick one slave of each group of leave slaves. E.g. always pick at lease one FRA4, AMS4 and LHR4 slave.

On 14/09/15 15:20, Shlomi Noach wrote:

Please explain "It might also be nice to pick at least one slave on each branch of the replication tree"

On Monday, September 14, 2015, Daniël van Eeden < notifications@github.com javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:

The orchestrator -c which-cluster-osc-slaves can pick slaves which are:

  • Delayed (OSC will wait until the table has reached all slaves...)
  • Have filters (See --check-replication-filters for pt-online-schema-change)

It might also be nice to pick at least one slave on each branch of the replication tree. Also I would like to configure and/or specify the number of slaves I want.

— Reply to this email directly or view it on GitHub https://github.com/outbrain/orchestrator/issues/107.

— Reply to this email directly or view it on GitHub < https://github.com/outbrain/orchestrator/issues/107#issuecomment-140072102 .

— Reply to this email directly or view it on GitHub https://github.com/outbrain/orchestrator/issues/107#issuecomment-140075405 .