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.

Sign up for GitHub

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

Jump to bottom

file write: exit Error #38

Open
1 task done
xandout opened this issue Aug 12, 2020 · 0 comments
Open
1 task done

file write: exit Error #38

xandout opened this issue Aug 12, 2020 · 0 comments

Comments

@xandout
Copy link

xandout commented Aug 12, 2020

Report

I am hitting an error when running rump in a Kubernetes pod(if that matters). The failure appears to happen here but also reports a TCP i/o timeout.

Can you confirm whether this is a filesystem i/o issue or an issue talking to Redis?

Is it possible to set timeouts higher and prevent this issue?

I see around a 7x increase in CPU usage but still not over 55%.

Node type: cache.m3.medium
Engine: Redis
Engine Version Compatibility: 2.8.24

file write: exit

signal: exit
read tcp 10.X.X.10:57824->10.Z.Z.145:6379: i/o timeout
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@xandout