Skip to content
This repository was archived by the owner on Dec 23, 2021. It is now read-only.
This repository was archived by the owner on Dec 23, 2021. It is now read-only.

After a deploy, have to wait for interval before any of the Workers gain a lease. #4

@kebbitt

Description

@kebbitt

Getting around this issue at the minute by setting interval to around 10 minutes. The system timer used only fires elapsed after first interval so if this was set to 45minutes for example, all workers would be dormant for this length of time.

It would be great if there was an option for 1st worker to attempt a lease as soon as deployed and then all workers to complete on next interval. Commonly we deploy to an Azure region one at a time and therefore all workers would not have a new version at the same time.

We don't use priorities at the minute, which are all set to zero, and realise this may be a complication for applications that do use.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions