BDR 1.0: background worker wants to start that should not be there

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

BDR 1.0: background worker wants to start that should not be there

Daniel Fink (PDF)

Hi all,

 

After I used bdr.bdr_part_by_node_names(p_nodes text[]) and removed the nodes from bdr.bdr_nodes table I still get log errors about the nonexistent pg_replication_slot:

 

< 2019-02-12 06:26:21.166 PST >LOG:  starting background worker process "bdr (6208877715678412212,1,22576474,)->bdr (6449651545875285115"

 

How does postgresql deduce which workers need starting?

Is there a table I am missing?

 

Best Regards,

 

DANIEL FINK
Senior Software Engineer

tel (+49) 89.767062.20
fax(+49) 89.767062.11
email [hidden email]

PDF Solutions GmbH 
(
a PDF Solutions Company)
Managing Director: Kimon Michaels
Schwanthalerstr.
10
D-80336 München, Germany  

München HRB 87307
DE 128214899

www.pdf.com

 


This message may contain confidential and privileged information. If it has been sent to you in error, please reply to advise the sender of the error and then immediately permanently delete it and all attachments to it from your systems. If you are not the intended recipient, do not read, copy, disclose or otherwise use this message or any attachments to it. The sender disclaims any liability for such unauthorized use. PLEASE NOTE that all incoming e-mails sent to PDF e-mail accounts will be archived and may be scanned by us and/or by external service providers to detect and prevent threats to our systems, investigate illegal or inappropriate behavior, and/or eliminate unsolicited promotional e-mails (“spam”). If you have any concerns about this process, please contact us at [hidden email].
Reply | Threaded
Open this post in threaded view
|

Re: BDR 1.0: background worker wants to start that should not be there

Alvaro Aguayo Garcia-Rada
Hi.

You have deleted the node from BDR setup, but you still have to delete it from the postgres logical replication:

SELECT * FROM pg_replication_slots;
SELECT pg_drop_replication_slot('YOURSLOT');

As a remark, based on my BDR experience, when your cluster has been damaged, your best option is to rebuild it.

Saludos,

Alvaro Aguayo
Jefe de Operaciones
Open Comb Systems E.I.R.L.

(+51-1) 337-7813 Anexo 4002
www.ocs.pe

----- Original Message -----
From: "Daniel Fink, PDF" <[hidden email]>
To: "pgsql-general" <[hidden email]>
Sent: Tuesday, 12 February, 2019 09:52:09
Subject: BDR 1.0: background worker wants to start that should not be there

Hi all,



After I used bdr.bdr_part_by_node_names(*p_nodes text[]*) and removed the
nodes from bdr.bdr_nodes table I still get log errors about the nonexistent
pg_replication_slot:



< 2019-02-12 06:26:21.166 PST >LOG:  starting background worker process
"bdr (6208877715678412212,1,22576474,)->bdr (6449651545875285115"



How does postgresql deduce which workers need starting?

Is there a table I am missing?



Best Regards,




*DANIEL FINK*

*Senior Software Engineer*

*tel* (+49) 89.767062.20
*fax*(+49) 89.767062.11
email [hidden email]

*PDF Solutions GmbH*
* (**a PDF Solutions Company)*
Managing Director: Kimon Michaels
Schwanthalerstr. 10
D-80336 München, Germany

München HRB 87307
DE 128214899

*www.pdf.com <http://www.pdf.com/>*

--
This message may contain confidential and privileged information. If it has
been sent to you in error, please reply to advise the sender of the error
and then immediately permanently delete it and all attachments to it from
your systems. If you are not the intended recipient, do not read, copy,
disclose or otherwise use this message or any attachments to it. The sender
disclaims any liability for such unauthorized use.  PLEASE NOTE that all
incoming e-mails sent to PDF e-mail accounts will be archived and may be
scanned by us and/or by external service providers to detect and prevent
threats to our systems, investigate illegal or inappropriate behavior,
and/or eliminate unsolicited promotional e-mails (“spam”).  If you have any
concerns about this process, please contact us at [hidden email]
<mailto:[hidden email]>.