Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Long Running Pulses will block other pulses from running #14613

Open
salsakran opened this issue Feb 1, 2021 · 3 comments
Open

Long Running Pulses will block other pulses from running #14613

salsakran opened this issue Feb 1, 2021 · 3 comments
Labels
.Performance Priority:P1 Security holes w/o exploit, crashing, setup/upgrade, login, broken common features, correctness Reporting/Pulses Now called Subscriptions Type:Bug Product defects

Comments

@salsakran
Copy link
Contributor

Describe the bug
There seems to be a blocking problem when a long running pulse on an issue prevents subsequent pulses from running and being sent.

Related Symptom Issues
This is believed to be the root cause for [TBF]
@salsakran salsakran added Type:Bug Product defects Priority:P1 Security holes w/o exploit, crashing, setup/upgrade, login, broken common features, correctness .Performance Reporting/Pulses Now called Subscriptions labels Feb 1, 2021
@paoliniluis

This comment has been minimized.

Sign in to view
@camsaul camsaul added this to the 0.38.1 milestone Feb 22, 2021
@camsaul camsaul modified the milestones: 0.38.1, 0.38.2 Mar 3, 2021
@camsaul camsaul modified the milestones: 0.38.2, 0.38.3 Mar 12, 2021
@rlotun rlotun removed this from the 0.38.3 milestone Apr 4, 2021
@paoliniluis paoliniluis removed their assignment Sep 23, 2021
@brunobergher

This comment has been minimized.

Sign in to view
@brunobergher brunobergher added Priority:P2 Average run of the mill bug and removed Priority:P1 Security holes w/o exploit, crashing, setup/upgrade, login, broken common features, correctness labels Sep 23, 2021
@flamber flamber added Priority:P1 Security holes w/o exploit, crashing, setup/upgrade, login, broken common features, correctness and removed Priority:P2 Average run of the mill bug labels Nov 1, 2021
@flamber
Copy link
Contributor

flamber commented Nov 1, 2021

Because pulses are being executed one after another, because only a single thread is available, then a single pulse in the beginning can block other all other pulses for a long time. This can be caused by a slow query or full pool.
Adding another thread could be a solution, but it would also cause more queries being executed at the same time.
image

@howonlee howonlee self-assigned this Jan 25, 2022
@howonlee howonlee removed their assignment Aug 12, 2022
@JesseSDevaney JesseSDevaney added the .Team/DashViz Dashboard and Viz team label Dec 14, 2023
@perivamsi perivamsi added .Team/BackendComponents also known as BEC and removed .Team/DashViz Dashboard and Viz team labels Jan 4, 2024
@albertoperdomo albertoperdomo mentioned this issue Jan 9, 2024
Open
@qnkhuat qnkhuat mentioned this issue Apr 24, 2024
Open
@darksciencebase darksciencebase removed the .Team/BackendComponents also known as BEC label Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
.Performance Priority:P1 Security holes w/o exploit, crashing, setup/upgrade, login, broken common features, correctness Reporting/Pulses Now called Subscriptions Type:Bug Product defects
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
10 participants
@rlotun @salsakran @perivamsi @brunobergher @howonlee @flamber @camsaul @paoliniluis @JesseSDevaney @darksciencebase