Обсуждение: BUG #14227: Former master not shot down

Поиск
Список
Период
Сортировка

BUG #14227: Former master not shot down

От
rob.nieuwenhuizen@mobpro.com
Дата:
VGhlIGZvbGxvd2luZyBidWcgaGFzIGJlZW4gbG9nZ2VkIG9uIHRoZSB3ZWJz
aXRlOgoKQnVnIHJlZmVyZW5jZTogICAgICAxNDIyNwpMb2dnZWQgYnk6ICAg
ICAgICAgIFJvYiBOaWV1d2VuaHVpemVuCkVtYWlsIGFkZHJlc3M6ICAgICAg
cm9iLm5pZXV3ZW5odWl6ZW5AbW9icHJvLmNvbQpQb3N0Z3JlU1FMIHZlcnNp
b246IDkuNS4zCk9wZXJhdGluZyBzeXN0ZW06ICAgRGViaWFuIFdoZWV6eQpE
ZXNjcmlwdGlvbjogICAgICAgIAoKSSBoYXZlIGEgbWFzdGVyIC8gc2xhdmUg
c2V0dXAgd2l0aCBhIGhvdC1zdGFuZGJ5IHNsYXZlcy4NCldoZW4gSSBkbyBh
IGZhaWxvdmVyIHRvIHRoZSBob3Qtc3RhbmRieSBzbGF2ZSB0aGUgc2xhdmUg
YmVjb21lcyBtYXN0ZXIsIGJ1dAp0aGUgZm9ybWVyIG1hc3RlciBpcyBub3Qg
c2hvdCBkb3duLg0KDQpUaGlzIHJlc3VsdHMgaW4gMiBtYXN0ZXIgc2VydmVy
cy4NCg0KTWF5YmUgdGhpcyBpcyBieSBkZXNpZ24sIG1heWJlIHRoZXJlIGlz
IGEgY29uZmlndXJhdGlvbiBmbGFnIEknbSBtaXNzaW5nLg0KDQoNCgoK

Re: BUG #14227: Former master not shot down

От
hubert depesz lubaczewski
Дата:
On Mon, Jul 04, 2016 at 01:44:38PM +0000, rob.nieuwenhuizen@mobpro.com wrote:
> I have a master / slave setup with a hot-standby slaves.
> When I do a failover to the hot-standby slave the slave becomes master, but
> the former master is not shot down.
> This results in 2 master servers.
> Maybe this is by design, maybe there is a configuration flag I'm missing.

this is not a bug, so it shouldn't be posted to -bugs. -general mailing
list seems to be better suited.

PostgreSQL doesn't kill old master, there is no such flag, because - how
could it?

By "do a failover" I assume you created trigger file on slave, or used
pg_ctl promote.
In both cases, it happens on slave, which can't connect and kill pg on
master.
Not to mention that it wouldn't always be what user really needs.

If you want to stop Pg on old master, ssh there, and kill pg yourself.

Best regards,

depesz

--
The best thing about modern society is how easy it is to avoid contact with it.
                                                             http://depesz.com/