hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "lujie (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-19004) master.RegionStates: THIS SHOULD NOT HAPPEN: unexpected
Date Fri, 13 Oct 2017 09:00:27 GMT

     [ https://issues.apache.org/jira/browse/HBASE-19004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

lujie updated HBASE-19004:
--------------------------
    Priority: Minor  (was: Major)

> master.RegionStates: THIS SHOULD NOT HAPPEN: unexpected 
> --------------------------------------------------------
>
>                 Key: HBASE-19004
>                 URL: https://issues.apache.org/jira/browse/HBASE-19004
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.2.6
>            Reporter: lujie
>            Priority: Minor
>
> When I send stop regionserver command, A log entry in master make me confused: THIS SHOULD
NOT HAPPEN: unexpected. I check the code,find the log printed in default condition(eg: if()
{} else if() {} else{log.warn()}). I think this condition should be handled
> {code:java}
> 2017-10-13 16:28:28,366 INFO  [ProcedureExecutor-1] zookeeper.ZKTableStateManager: Moving
table TestTable state from null to ENABLING
> 2017-10-13 16:28:28,387 INFO  [ProcedureExecutor-1] master.AssignmentManager: Bulk assigning
1 region(s) across 3 server(s), round-robin=true
> 2017-10-13 16:28:28,388 INFO  [hadoop11,16000,1507883241250-GeneralBulkAssigner-0] master.AssignmentManager:
Assigning 1 region(s) to hadoop11,16020,1507883241942
> 2017-10-13 16:28:28,394 INFO  [hadoop11,16000,1507883241250-GeneralBulkAssigner-0] master.RegionStates:
Transition {2aaaf8304f2b09288f528ac0f105cc01 state=OFFLINE, ts=1507883308388, server=null}
to {2aaaf8304f2b09288f528ac0f105cc01 state=PENDING_OPEN, ts=1507883308394, server=hadoop11,16020,1507883241942}
> 2017-10-13 16:28:28,585 INFO  [AM.ZK.Worker-pool2-t10] master.RegionStates: Transition
{2aaaf8304f2b09288f528ac0f105cc01 state=PENDING_OPEN, ts=1507883308394, server=hadoop11,16020,1507883241942}
to {2aaaf8304f2b09288f528ac0f105cc01 state=OPENING, ts=1507883308585, server=hadoop11,16020,1507883241942}
> 2017-10-13 16:28:29,163 INFO  [AM.ZK.Worker-pool2-t11] master.RegionStates: Transition
{2aaaf8304f2b09288f528ac0f105cc01 state=OPENING, ts=1507883308585, server=hadoop11,16020,1507883241942}
to {2aaaf8304f2b09288f528ac0f105cc01 state=OPEN, ts=1507883309163, server=hadoop11,16020,1507883241942}
> 2017-10-13 16:28:36,517 INFO  [main-EventThread] zookeeper.RegionServerTracker: RegionServer
ephemeral node deleted, processing expiration [hadoop11,16020,1507883241942]
> 2017-10-13 16:28:37,428 INFO  [ProcedureExecutor-2] procedure.ServerCrashProcedure: Start
processing crashed hadoop11,16020,1507883241942
> 2017-10-13 16:28:37,689 INFO  [ProcedureExecutor-4] master.SplitLogManager: dead splitlog
workers [hadoop11,16020,1507883241942]
> 2017-10-13 16:28:37,693 INFO  [ProcedureExecutor-4] master.SplitLogManager: hdfs://hadoop11:29000/hbase/WALs/hadoop11,16020,1507883241942-splitting
is empty dir, no logs to split
> 2017-10-13 16:28:37,695 INFO  [ProcedureExecutor-4] master.SplitLogManager: Started splitting
0 logs in [hdfs://hadoop11:29000/hbase/WALs/hadoop11,16020,1507883241942-splitting] for [hadoop11,16020,1507883241942]
> 2017-10-13 16:28:37,701 INFO  [ProcedureExecutor-4] master.SplitLogManager: finished
splitting (more than or equal to) 0 bytes in 0 log files in [hdfs://hadoop11:29000/hbase/WALs/hadoop11,16020,1507883241942-splitting]
in 6ms
> 2017-10-13 16:28:37,807 WARN  [ProcedureExecutor-4] master.RegionStates: THIS SHOULD
NOT HAPPEN: unexpected {2aaaf8304f2b09288f528ac0f105cc01 state=OPEN, ts=1507883309163, server=hadoop11,16020,1507883241942}
> 2017-10-13 16:28:37,923 INFO  [ProcedureExecutor-4] procedure.ServerCrashProcedure: Finished
processing of crashed hadoop11,16020,1507883241942
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message