Opened 4 years ago

Last modified 18 months ago

#10155 needs_information enhancement

Allow delayed node start

Reported by: sysrqb Owned by:
Priority: Medium Milestone:
Component: Core Tor/Chutney Version:
Severity: Normal Keywords:
Cc: mail@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

It will be useful to allow nodes to be started after a certain amount of time, especially when interested in its effect on the consensus.

Child Tickets

Change History (6)

comment:1 Changed 4 years ago by sysrqb

Status: newneeds_review

If the node is created with a delay=x value then chutney forks a child, sleeps for x seconds and then execs tor. This likely can be improved. Branch bug10155 in my repo.

comment:2 Changed 4 years ago by cbaines

Cc: mail@… added

comment:3 Changed 4 years ago by nickm

It looks like we've diverged a little; fad78679d34e4f345b13942e9bbdc0ddbbb52e13 is the commit I should be reviewing here.

I like the idea for the feature, but I think this argues strongly for some kind of scheduler/driver-based thing, rather than a bunch of fork/sleep/exit backends.

Then again, nobody's written the scheduler/driver thing, and this would work today, I bet.

What tests have you done with this?

How well does this work if you say "chutney status" or "chutney stop" before the delayed tor nodes have started?

comment:4 Changed 20 months ago by teor

Severity: Normal
Status: needs_reviewneeds_information

comment:5 Changed 18 months ago by nickm

Owner: nickm deleted
Status: needs_informationassigned

Remove myself as owner from old chutney tickets; that's not what we use owner for.

comment:6 Changed 18 months ago by nickm

Status: assignedneeds_information
Note: See TracTickets for help on using tickets.