Feature Question -- ability to specify HEARTBEAT_INTERVAL, MIN_ELECTION_TIMEOUT and MAX_ELECTION_TIMEOUT values.

[nehemming]

Hi - our question is "is it possible to specify for a cluster option values for

• HEARTBEAT_INTERVAL
• MIN_ELECTION_TIMEOUT
• MAX_ELECTION_TIMEOUT

In place of the default hard coded values. We are looking at a use case where a slower heartbeat interval would suffice. Currently the only solution is to fork and update constants.

Is this on a feature roadmap or would you consider a PR to making the change ... and if so any advise on how you would suggest it is done?

Thanks.

[abemedia]

Simply changing them from const to var would be great!

[derekcollison]

We have some ideas for future functionality that can leverage the JetStream subsystem. Not much work is being put into this library as of late, but I would be happy to review any PRs.