Alexsandr

@tgross found this issue because have the same case described here. what's about docs? i think it's really confusing now that is not described in official docs when you setup...

Perhaps this is true. I think this does not depend on the volume of log entries or even the overall volume of processed log records. Yes, if you enable the...

Hi! Thanks for quick reply! What we changed (all masters in cluster restarted and configs updated): ``` server { heatbeat_grace = 60s } ``` and than we setup the following...

>Can you describe this? There's a good bit of difference between a host reboot and restarting the Nomad agent, so I want to make sure that's well-covered. I mean reboot...

@tgross For now we are back to the original scheme, without any manipulations with heatbeat_grace and without the disconnect block, but I still have the results of tests with the...

@tgross Thanks a lot for quick responses! How quickly can we expect this situation to be resolved in theory? I assume you classify it as "low priority", but if possible,...

@tgross I thought about the phrase for a long time > things are going wrong for the reboot case is step (6). That's because the host has been rebooted, so...

One more question. Can we somehow **cache secrets on a remote server**, say using nomad\vault binary? so that **secrets remain on the server side even after a reboot.** Because jobs...

any response on this? or this is normal behavior?

Okay, here is example token creation with policies to test: create few namespaces (stage-example, dev-example, dev-example2, stage-example2) policy 1: ``` namespace "stage-example" { policy = "read" capabilities = ["alloc-exec"] }...