Re-enable direct gets and update nats-server and nats.go versions #281
Conversation
|
@brandond I check out the Drone CI and noticed that for the NATS 2.10.11, the API server was failing to come up, but its not clear why: |
|
@bruth as per #275 (comment) it sounds like this does not resolve the error? |
|
Checking it out again. |
Signed-off-by: Byron Ruth <byron@nats.io>
Signed-off-by: Byron Ruth <byron@nats.io>
Signed-off-by: Byron Ruth <byron@nats.io>
bruth
force-pushed
the
update-nats-versions
branch
from
5f60b40
to
a92110e
Compare
bruth
changed the title
|
Found the root cause.. I had disabled an internal API that the KV bucket normally uses a while back since it was buggy at the time. However that had the side effect of having certain requests time out since directs gets were disabled. The error reporting simply appears as a timeout since there is not receiver of that direct get API. I validated the timeout no longer occurs when creating the health check key-value pair which will prevent the issue noted in #274. This has been likely affecting all deployments of kine+NATS. Also confirmed the CI passed this time. |
|
I will update with an additional commit shortly to ensure that API is enabled for existing KV buckets. |
Signed-off-by: Byron Ruth <byron@nats.io>
|
@brandond Assuming CI passes, this is now ready to be reviewed and merged. |
No description provided.