The session are not set with TTL=15s so it'

[manish2479]

Hi

I have tried this consul-do tool and it's working fine but I am seeing one issue is that it doesn't clears the old session and the session created for that node has to be up online otherwise the job fails when it's executed from other node. So I think it needs TTL to be set to 15s for each session ID and then it expires the session and delete the key.

[zeroXten]

Thanks for the bug report. Realistically I'm not sure if or when I'll be able to take a look at this. I'm not using Consul at the moment so I don't have somewhere to test any fixes. I'd happily merge a pull request if you're in a position to create one.

[gneill794]

Hi manish2479,

I know I am responding to an old post, sorry about that. If a TTL were to be set... and the session was automatically deleted/released, I believe the purpose of gaining leadership in the first place could be lost.

For example, What would happen if the process you are running under the current leader takes longer than the TTL which was set?

Would you happen to remember the use case which made you think it's a bug?

I am just guessing here ... maybe you removed the cron entry from the current leader? In this case, there's really no way to automatically know you did that. This would force you to manually remove the lock and let the next 'run' find a leader. Based on what I have seen, when the consul node goes offline it will invalidate the session.