hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3909) Add dynamic config
Date Mon, 27 Jan 2014 19:30:43 GMT

    [ https://issues.apache.org/jira/browse/HBASE-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883160#comment-13883160
] 

stack commented on HBASE-3909:
------------------------------

bq. That's a pretty big hole. What happens if there is a fail over?

The failed-over master will be missing the config.  A workaround would be the operator restarting
the backup masters when master config changed.  Can add this to the release notes and address
it better in a second issue (backup masters are in general on hbaseadmins blindside -- need
to fix).

> Add dynamic config
> ------------------
>
>                 Key: HBASE-3909
>                 URL: https://issues.apache.org/jira/browse/HBASE-3909
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: stack
>            Assignee: Subbu M Iyer
>         Attachments: 3909-102812.patch, 3909-102912.patch, 3909-v1.patch, 3909.v1, 3909_090712-2.patch,
HBASE-3909-backport-from-fb-for-trunk-2.patch, HBASE-3909-backport-from-fb-for-trunk.patch,
HBase Cluster Config Details.xlsx, patch-v2.patch, testMasterNoCluster.stack
>
>
> I'm sure this issue exists already, at least as part of the discussion around making
online schema edits possible, but no hard this having its own issue.  Ted started a conversation
on this topic up on dev and Todd suggested we lookd at how Hadoop did it over in HADOOP-7001



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message