apache
Bookie should not shutdown when disk IO error
FEATURE REQUEST
-
Please describe the feature you are requesting. In current Bookkeeper implementation, when disk occurs IO error, eg, disk readonly failure or disk sector failure, it will trigger bookie shutdown and the bookie can't startup before the bad disk kicked off by admin. In my production, we has 24 disks per node and the disks' failure rate is high enough. If the bookie shutdown when occurs disk IO error, it will trigger Bookkeeper cluster to re-replicate the lost data, which belongs to the shutdown bookie. However the amount of data belongs to the bookie will be tens of TB, which will cause Bookkeeper cluster busy and make it unstable.
-
Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). In my env, i should solved this problem before bring it to production.
-
Provide any additional detail on your proposed use case for this feature. Do you have any ideas or plans to add this feature, or we can discuss the feature design.
Could you give me some suggestion? @sijie @merlimat @ivankelly @eolivelli @jiazhai
in my opinion we do not have tools and features to handle this case. but definitely we should do something I have only experience of single disk Bookies
probably @jvrao @karanmehta93 or @merlimat and @sijie may have more experience to share
@hangc0276 as we discussed offline, we should mark a disk as broken and trigger auto-recovery to replicate the entries on that disk.
@hangc0276 as we discussed offline, we should mark a disk as broken and trigger auto-recovery to replicate the entries on that disk.
@sijie @hangc0276 we also meet this problem in our production.
Is it possible to add such feature in bookie? Such as dfs.datanode.failed.volumes.tolerated in hdfs.
