Skip to content

the behavior when start_server receives multiple HUP signals #9

Description

@harukasan

go-server-starter implements the different to Server::Starter's one.

p5-server-starter behavior:

         old workers   action
-------  ------------  ----------------------------------------------------
1st HUP             0  spawn new worker and send TERM signal to old workers
2nd HUP             1  spawn new worker and send TERM signal to old workers
3rd HUP             2  spwan new worker and send TERM signal to old workers (stop one)
4th HUP             2  ...

go-server-starter behavior:

         old workers   action
-------  ------------  ----------------------------------------------------
1st HUP             0  spawn new worker and send TERM signal to old workers
2nd HUP             1  no action
3nd HUP             1  no action (stop one old worker)
4th HUP             0  spawn new worker and send TERM signal to old workers
                       when the all old worker exit.

I want to use the original perl's behavior with go-server-starter.

I also notice that restart = 2 is not used for now. Should we implement other options and set restart = 2?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    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