Alain,
Can you post your mdadm --detail /dev/md0 output here as well as your
iostat -x -d when that happens. A bad ephemeral drive on EC2 is not unheard
of.
Alexis | @alq | http://datadog.com
P.S. also, disk utilization is not a reliable metric, iostat's await and
svctm are more useful imho.
and insert.
--
Alexis Lê-Quôc | Datadog, Inc. | @alq
(response, id, msg.getFrom());
43 }
44 }
Before I dig deeper in the code, has anybody dealt with this before?
Thanks,
--
Alexis Lê-Quôc
%
92535295865117307932921825928971026432
192.168.0.5 Up Normal 263.91 MB 12.28%
113427455640312821154458202477256070485
192.168.0.6 Up Normal 26.21 MB 8.33%
127605887595351923798765477786913079296
--
Dikang Gu
0086 - 18611140205
--
Alexis Lê-Quôc (@alq) | Datadog
this be caused by old hinted handoffs for 2.3.4.193 that were processed
at that time, causing the rest of the nodes to think that the 2.3.4.193 is
still present (albeit down)?
Should cleanup be run periodically? I run repair every few days (my
gcgraceperiod is 10 days).
--
Alexis Lê-Quôc (@datadoghq
