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

Added warning and info for queue factory. #194

Merged
merged 8 commits into from
Jan 18, 2024
Merged

Conversation

kepol
Copy link
Contributor

@kepol kepol commented Nov 3, 2023

Followup from #149

Adding setting to purger README and add warning across all admin pages if this isn't set since it will affect performance.

$settings['queue_service_quant_seed_worker'] = 'quant.queue_factory';

Drupal.org issue: https://www.drupal.org/project/quantcdn/issues/3398935

Screenshot 2023-11-05 at 1 47 52 PM

@kepol kepol added enhancement New feature or request needs review labels Nov 3, 2023
@kepol
Copy link
Contributor Author

kepol commented Nov 5, 2023

Note that I found this major bug when testing this so maybe we should fix that prior to showing this warning message:

https://www.drupal.org/project/quantcdn/issues/3399266

Copy link
Contributor

@steveworley steveworley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a minor discussion point on this one @kepol.

the next core cron run. You can run the cron manually or wait for the site's
cron to run on its regular schedule. For the latter, note that the static
content will be out-of-sync with the Drupal site until the cron runs, which may
cause confusion in some cases. Thus, it is recommended that cron is run right
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would say that the recommendation is to have the quant queue run drush command running separately to core cron and having its frequency increased rather than running cron after a node save.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gotcha... could you revise how you'd like it?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually, I can revise

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@steveworley I changed it to:

To ensure that queued content is processed in a timely manner, you can set up a
Quant cron process that is separate from the core cron which just processes the
Quant queue. This Quant cron can be run more regularly than the core cron.

If you want any tweaks, feel free to suggest specific changes.

@kepol kepol self-assigned this Jan 4, 2024
@kepol kepol requested a review from steveworley January 7, 2024 01:10
@kepol kepol dismissed steveworley’s stale review January 9, 2024 20:27

See latest code changes that address this.

@kepol
Copy link
Contributor Author

kepol commented Jan 18, 2024

I'm going to merge this because I think the text is okay.

@kepol kepol merged commit c039587 into 8.x-1.x Jan 18, 2024
2 checks passed
@kepol kepol removed their assignment Jan 19, 2024
@kepol kepol deleted the feature/queue-unique-info branch January 21, 2024 18:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Drupal 8 / 9 / 10 enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants