Jira (PDB-4974) Wait on schedulers to shut down

18 views
Skip to first unread message

Rob Browning (Jira)

unread,
Dec 2, 2020, 1:23:03 PM12/2/20
to puppe...@googlegroups.com
Rob Browning created an issue
 
PuppetDB / Bug PDB-4974
Wait on schedulers to shut down
Issue Type: Bug Bug
Assignee: Unassigned
Created: 2020/12/02 10:22 AM
Priority: Normal Normal
Reporter: Rob Browning

Although we'd expected to be waiting for our schedulers (at-at pools) to stop before returning from our start/stop methods, we weren't because at-at runs the relevant ScheduledThreadPoolExecutor shutdown function in a future and returns immediately.

 

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo

Rob Browning (Jira)

unread,
Dec 2, 2020, 1:25:02 PM12/2/20
to puppe...@googlegroups.com
Rob Browning assigned an issue to Rob Browning
Change By: Rob Browning
Assignee: Rob Browning

Rob Browning (Jira)

unread,
Dec 2, 2020, 2:27:03 PM12/2/20
to puppe...@googlegroups.com
Rob Browning updated an issue
Change By: Rob Browning
Epic Link: PDB-4969

Issue Updates (Jira)

unread,
Dec 16, 2020, 1:47:03 PM12/16/20
to puppe...@googlegroups.com
Issue Updates updated an issue
    • Address not found **

Your message wasn't delivered to k...@puppet.com because the address couldn't be found, or is unable to receive mail.

Learn more here: https://support.google.com/mail/?p=NoSuchUser

The response was:

550 5.1.1 The email account that you tried to reach does not exist. Please try double-checking the recipient's email address for typos or unnecessary spaces. Learn more at https://support.google.com/mail/?p=NoSuchUser j205sor1292587pfd.41 - gsmtp

----- Message truncated -----

Change By: Issue Updates
Attachment: icon.png

Issue Updates (Jira)

unread,
Dec 16, 2020, 1:47:05 PM12/16/20
to puppe...@googlegroups.com
Issue Updates updated an issue
    • Address not found **

Your message wasn't delivered to wy...@puppet.com because the address couldn't be found, or is unable to receive mail.

Learn more here: https://support.google.com/mail/?p=NoSuchUser

The response was:

550 5.1.1 The email account that you tried to reach does not exist. Please try double-checking the recipient's email address for typos or unnecessary spaces. Learn more at https://support.google.com/mail/?p=NoSuchUser o8sor1623465plk.56 - gsmtp

----- Message truncated -----

Change By: Issue Updates
Attachment: icon.png
Add Comment Add Comment
 

Zachary Kent (Jira)

unread,
Jan 13, 2021, 2:11:04 PM1/13/21
to puppe...@googlegroups.com
Zachary Kent updated an issue
Change By: Zachary Kent
Sprint: HA 2021-01-27

Eric Thompson (Jira)

unread,
Jan 27, 2021, 2:18:04 PM1/27/21
to puppe...@googlegroups.com
Eric Thompson updated an issue
Change By: Eric Thompson
Sprint: HA 2021-01-27 , HA 2021-02-10

Austin Blatt (Jira)

unread,
Feb 5, 2021, 12:20:04 PM2/5/21
to puppe...@googlegroups.com
Austin Blatt updated an issue
Change By: Austin Blatt
Fix Version/s: PDB 7.1.0
Fix Version/s: PDB 6.14.0

Rob Browning (Jira)

unread,
Feb 8, 2021, 4:27:04 PM2/8/21
to puppe...@googlegroups.com
Rob Browning updated an issue
Change By: Rob Browning
Release Notes: Bug Fix
Release Notes Summary: Previously an attempt to stop (or restart) PuppetDB might appear to succeed, even though some of its components were actually still running.  That's because PuppetDB wasn't actually waiting for some of the internal tasks to finish as had been expected.  Now PuppetDB should block during stop or restart until all of the components have actually shut down.  This issue is a likely contributor to some cases where PuppetDB appeared to restart/reload successfully, but sync never started working again.
Reply all
Reply to author
Forward
0 new messages