forFile and forUrl are not interrupted if scan nodes are updated #2
Description
If scan nodes are updated, existing scans and new requests should not be impacted - it should be seamless.
Acceptance criteria:
- New requests are not impacted by scan node updates
- Long requests (< grace peroid) are not impacted by scan node updates
Test scenarios:
- Repeatedly scan a small files (< 1 MB), 8 clients
- Repeatedly scan a big file (scan duration > 20s), 1 client