Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
1.1.0
-
None
-
None
Description
In one of my clusters, observed this situation.
This issue looks to be due to time out in ResponseProcesser at client side, it is marking first DataNode as bad.
This happens in 20.2 version. This can be there in branch-1 as well and will check for trunk.