Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cueball HTTP agent config missing pinger or TCP keepalives #42

Open
arekinath opened this issue Oct 21, 2019 · 0 comments
Open

cueball HTTP agent config missing pinger or TCP keepalives #42

arekinath opened this issue Oct 21, 2019 · 0 comments

Comments

@arekinath
Copy link
Contributor

arekinath commented Oct 21, 2019

The current CueballHttpAgent config we're using in cloudapi is missing a pinger or TCP keepalive settings, which means that we can easily get "zombie" connections or races when cloudapi is talking to other components (like imgapi or napi) -- while cloudapi is writing a request out to a socket, the other end is closing it, and we get ECONNRESET errors.

It seems like all of the downstream services have a /ping endpoint, or at least don't respond with an error to that URI, so we should just need to add:

        "tcpKeepAliveInitialDelay": 10000,
        "ping": "/ping",
        "pingInterval": 60000,

We'll have to update the version of cueball as well, since the version we're using at the moment (2.1.1) has a bug that causes pingers to misbehave (TritonDataCenter/node-cueball#102)

arekinath added a commit to eait-itig/sdc-cloudapi that referenced this issue May 19, 2021
danmcd pushed a commit that referenced this issue May 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant