[jira] [Updated] (HBASE-21214) [hbck2] setTableState just sets hbase:meta state, not in-memory state
[ https://issues.apache.org/jira/browse/HBASE-21214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-21214: --- Fix Version/s: 2.2.0 3.0.0 > [hbck2] setTableState just sets hbase:meta state, not in-memory state > - > > Key: HBASE-21214 > URL: https://issues.apache.org/jira/browse/HBASE-21214 > Project: HBase > Issue Type: Sub-task > Components: amv2, hbck2 >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 3.0.0, 2.2.0, 2.1.1 > > Attachments: 21214.patch, HBASE-21214.master.001.patch > > > Means that we have to go get another Master to see the table state change > because in-memory state is still pegged at the old value. > TODO: Check the is_enabled/is_disabled shell commands to make sure they are > reading from the right place. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-21214) [hbck2] setTableState just sets hbase:meta state, not in-memory state
[ https://issues.apache.org/jira/browse/HBASE-21214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-21214: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed to branch-2.1+. Thanks for review (Pushed patch that fixes the findbugs). > [hbck2] setTableState just sets hbase:meta state, not in-memory state > - > > Key: HBASE-21214 > URL: https://issues.apache.org/jira/browse/HBASE-21214 > Project: HBase > Issue Type: Sub-task > Components: amv2, hbck2 >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.1.1 > > Attachments: 21214.patch, HBASE-21214.master.001.patch > > > Means that we have to go get another Master to see the table state change > because in-memory state is still pegged at the old value. > TODO: Check the is_enabled/is_disabled shell commands to make sure they are > reading from the right place. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-21214) [hbck2] setTableState just sets hbase:meta state, not in-memory state
[ https://issues.apache.org/jira/browse/HBASE-21214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-21214: -- Attachment: HBASE-21214.master.001.patch > [hbck2] setTableState just sets hbase:meta state, not in-memory state > - > > Key: HBASE-21214 > URL: https://issues.apache.org/jira/browse/HBASE-21214 > Project: HBase > Issue Type: Sub-task > Components: amv2, hbck2 >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.1.1 > > Attachments: 21214.patch, HBASE-21214.master.001.patch > > > Means that we have to go get another Master to see the table state change > because in-memory state is still pegged at the old value. > TODO: Check the is_enabled/is_disabled shell commands to make sure they are > reading from the right place. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-21214) [hbck2] setTableState just sets hbase:meta state, not in-memory state
[
https://issues.apache.org/jira/browse/HBASE-21214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-21214:
--
Assignee: stack
Status: Patch Available (was: Open)
Small patch.
Uses TableStateManager setting states so in-memory state is updated too. If
just need to set state in hbase:meta, could use shell?
{code}
scan 'hbase:meta', 'TABLENAME,,', {LIMIT => 1, COLUMN=> 'table:state'}
{code}
The above is cryptic but returns the row for table state.
Can then do:
{code}
put 'hbase:meta', ROW_FOUND_ABOVE 'table:state', ENABLED
{code}
Again cryptic. Could make it 'nicer' but meantime could write above into the
hbck2 HOWTO if setting state in hbase:meta only is what is wanted.
> [hbck2] setTableState just sets hbase:meta state, not in-memory state
> -
>
> Key: HBASE-21214
> URL: https://issues.apache.org/jira/browse/HBASE-21214
> Project: HBase
> Issue Type: Sub-task
> Components: amv2, hbck2
>Reporter: stack
>Assignee: stack
>Priority: Major
> Fix For: 2.1.1
>
> Attachments: 21214.patch
>
>
> Means that we have to go get another Master to see the table state change
> because in-memory state is still pegged at the old value.
> TODO: Check the is_enabled/is_disabled shell commands to make sure they are
> reading from the right place.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-21214) [hbck2] setTableState just sets hbase:meta state, not in-memory state
[ https://issues.apache.org/jira/browse/HBASE-21214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-21214: -- Attachment: 21214.patch > [hbck2] setTableState just sets hbase:meta state, not in-memory state > - > > Key: HBASE-21214 > URL: https://issues.apache.org/jira/browse/HBASE-21214 > Project: HBase > Issue Type: Sub-task > Components: amv2, hbck2 >Reporter: stack >Priority: Major > Fix For: 2.1.1 > > Attachments: 21214.patch > > > Means that we have to go get another Master to see the table state change > because in-memory state is still pegged at the old value. > TODO: Check the is_enabled/is_disabled shell commands to make sure they are > reading from the right place. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
