Jira (PDB-5349) PuppetDB blocks primary on restart

[Margaret Lee (Jira)]

Margaret Lee created an issue

PuppetDB / PDB-5349 PuppetDB blocks primary on restart Issue Type: Improvement Assignee: Unassigned Created: 2021/10/27 8:07 AM Priority: Normal Reporter: Margaret Lee PuppetDB Restart with Replica - PuppetDB on Primary comes up "blocking" until the Replica comes up - this elongates outages and restarts. To avoid this we have to stop the replica puppetdb and then restart primary. It would be really helpful if puppetdb didn't block the primary on restart Add Comment

This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)

[David McTavish (Jira)]

David McTavish updated an issue

PuppetDB / PDB-5349 PuppetDB blocks primary on restart

Change By: David McTavish Priority: Normal High

Add Comment

This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)

[David McTavish (Jira)]

David McTavish updated an issue

PuppetDB / PDB-5349 PuppetDB blocks primary on restart

Change By: David McTavish Sprint: HAHA/Grooming

Add Comment

[Nick Walker (Jira)]

Nick Walker commented on PDB-5349

Re: PuppetDB blocks primary on restart The track we've gone down on this issue is basically to make the blocking portion of startup go as fast as possible. We don't sync reports during that blocking part now, we stopped doing GC on startup and possibly other small improvements. It's not clear that starting without syncing "enough" data is safe to allow agents to query against.

Add Comment