stickermule / rump

Hot sync two Redis servers using dumps.
MIT License
491 stars 94 forks source link

file write: exit Error #38

Open xandout opened 4 years ago

xandout commented 4 years ago

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