Skip to content

forFile and forUrl are not interrupted if scan nodes are updated #2

@pstadermann

Description

@pstadermann

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions