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.

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

Do not check if any archive is running when a segment is forced #15955

Merged
merged 1 commit into from Jun 29, 2020

Conversation

tsteur
Copy link
Member

@tsteur tsteur commented May 15, 2020

From a support request. eg user has

6 * * * * * console core:archive --force-idsegment=1
6 * * * * * console core:archive --force-idsegment=2
6 * * * * * console core:archive --force-idsegment=3

Then currently it would skip some segments because it checks if any archive is already running. After the launching the first one for segment 1, an archive is already running and would probably never launch 2nd and 3rd segment AFAIK.

@mattab

@tsteur tsteur added the Needs Review PRs that need a code review label May 15, 2020
@tsteur tsteur added this to the 3.13.6 milestone May 15, 2020
@tsteur
Copy link
Member Author

tsteur commented May 17, 2020

@mattab fyi waiting for your confirmation that it fixes the user's issue before merging

@sgiehl sgiehl modified the milestones: 3.13.6, 3.13.7 Jun 8, 2020
@tsteur tsteur merged commit f165cf7 into 3.x-dev Jun 29, 2020
@tsteur tsteur deleted the archiveforcedsegment branch June 29, 2020 21:26
jbuget pushed a commit to 1024pix/pix-analytics that referenced this pull request Sep 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Review PRs that need a code review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants