-
-
Notifications
You must be signed in to change notification settings - Fork 52
Allow users to run crawls with 1 or 2 browser windows #2627
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
Conversation
@tw4l Updated to set the maximum width to the screencast image width: ![]() |
This will keep scale and browserWindows from getting out of sync when the number of workers per pod on an instance changes.
Comment out unsetting of scale for now for easier testing on dev
…ces, then in multiples through max
8cb422e
to
aab9f5a
Compare
Co-authored-by: Tessa Walsh <tessa@bitarchivist.net>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good testing locally, if it's easy to do we should add a deprecation notice for the scale
API field.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Nice work, tested on dev with different number of windows!
) - follow up to #2627 - use qa_num_browser_windows to set exact number of QA browsers, fallback to qa_scale - set num_browser_windows and num_browsers_per_pod using crawler / qa values depending if QA crawl - scale_from_browser_windows() accepts optional browsers_per_pod if dealing with possible QA override - store 'desiredScale' in CrawlStatus to avoid recomputing for later scale resolving - ensure status.scale is always the actual scale observed
Fixes #2425
Changed
browserWindows
fromscale
for existing workflows and crawls)scale
in addition tobrowserWindows
in input models for creating and updating workflows and re-adjusting live crawl scale for backwards compatibilitymax_browser_windows
value to Helm chart, but calculates the value frommax_crawl_scale
as fallback for users with that value already set in local chartscrawler_browser_instances
or any value belowcrawler_browser_instances
for browser windows. For instance, withcrawler_browser_instances=4
andmax_browser_windows=8
, the user would be presented with the following options: 1, 2, 3, 4, 8message