[
https://issues.apache.org/jira/browse/HBASE-26883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
May updated HBASE-26883:
------------------------
Description:
I have a hbae cluster of 2 master nodes (C1HM1:172.0.0.2 and C1HM2:172.0.0.3)
and 3 slave nodes (C1RS1:172.0.0.4, C1RS2:172.0.0.5, C1RS3:172.0.0.6). The
following is the bug triggering process:
# the active master is C1HM1, the meta server is C1RS2
# client requests to create a table "FAVMyInfo"
# {color:#de350b}2022-03-24 01:44:54,317 [MyTest] - INFO - Going to crash node
172.25.0.5（table "FAVMyInfo" exists in the ZooKeeper at this time）{color}
# C1HM1 assigns meta regions to C1RS3
# client receives ACK about creating table "FAVMyInfo", and then makes some
changes to "FAVMyInfo"
# 2022-03-24 01:46:20,664 [MyTest] - INFO - Client has disabled table
"FAVMyInfo" and requests to truncate "FAVMyInfo"
# {color:#de350b}2022-03-24 01:46:23,302 [MyTest] - INFO - Going to crash node
172.25.0.2 (at this time, table "FAVMyInfo" does not exist in the
ZooKeeper){color}
# {color:#de350b}2022-03-24 01:46:46,023 [MyTest] - INFO - Going to crash node
172.25.0.6{color}
# 2022-03-24 01:48:13,497 [MyTest] - INFO - client receives response for
truncating "FAVMyInfo", no Exceptions here. Then client requests to get a row
from "FAVMyInfo", but gets {color:#FF0000}"TableNotFoundException:
FAVMyInfo"{color}
#
was:
I have a hbae cluster of 2 master nodes (C1HM1:172.0.0.2 and C1HM2:172.0.0.3)
and 3 slave nodes (C1RS1:172.0.0.4, C1RS2:172.0.0.5, C1RS3:172.0.0.6). The
following is the bug triggering process:
# the active master is C1HM1, the meta server is C1RS2
# client requests to create a table "FAVMyInfo"
# 2022-03-24 01:44:54,317 [MyTest] - INFO - Going to crash node
172.25.0.5（table "FAVMyInfo" exists in the ZooKeeper at this time）
# C1HM1 assigns meta regions to C1RS3
# client receives ACK about creating table "FAVMyInfo", and then makes some
changes to "FAVMyInfo"
# 2022-03-24 01:46:20,664 [MyTest] - INFO - Client has disabled table
"FAVMyInfo" and requests to truncate "FAVMyInfo"
# 2022-03-24 01:46:23,302 [MyTest] - INFO - Prepare to crash node 172.25.0.2
(at this time, table "FAVMyInfo" does not exist in the ZooKeeper)
# 2022-03-24 01:46:46,023 [MyTest] - INFO - Prepare to crash node 172.25.0.6
# 2022-03-24 01:48:13,497 [MyTest] - INFO - client receives response for
truncating "FAVMyInfo", no Exceptions here. Then client requests to get a row
from "FAVMyInfo", but gets {color:red}"TableNotFoundException: FAVMyInfo"{color}
#
> Crash HM and META-RS when truncating table causes data loss
> -----------------------------------------------------------
>
> Key: HBASE-26883
> URL: https://issues.apache.org/jira/browse/HBASE-26883
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.4.8
> Reporter: May
> Priority: Major
>
> I have a hbae cluster of 2 master nodes (C1HM1:172.0.0.2 and C1HM2:172.0.0.3)
> and 3 slave nodes (C1RS1:172.0.0.4, C1RS2:172.0.0.5, C1RS3:172.0.0.6). The
> following is the bug triggering process:
> # the active master is C1HM1, the meta server is C1RS2
> # client requests to create a table "FAVMyInfo"
> # {color:#de350b}2022-03-24 01:44:54,317 [MyTest] - INFO - Going to crash
> node 172.25.0.5（table "FAVMyInfo" exists in the ZooKeeper at this time）{color}
> # C1HM1 assigns meta regions to C1RS3
> # client receives ACK about creating table "FAVMyInfo", and then makes some
> changes to "FAVMyInfo"
> # 2022-03-24 01:46:20,664 [MyTest] - INFO - Client has disabled table
> "FAVMyInfo" and requests to truncate "FAVMyInfo"
> # {color:#de350b}2022-03-24 01:46:23,302 [MyTest] - INFO - Going to crash
> node 172.25.0.2 (at this time, table "FAVMyInfo" does not exist in the
> ZooKeeper){color}
> # {color:#de350b}2022-03-24 01:46:46,023 [MyTest] - INFO - Going to crash
> node 172.25.0.6{color}
> # 2022-03-24 01:48:13,497 [MyTest] - INFO - client receives response for
> truncating "FAVMyInfo", no Exceptions here. Then client requests to get a row
> from "FAVMyInfo", but gets {color:#FF0000}"TableNotFoundException:
> FAVMyInfo"{color}
> #
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
