[
https://issues.apache.org/jira/browse/HBASE-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215243#comment-13215243
]
Mubarak Seyed commented on HBASE-4991:
--------------------------------------
bq. could use: 'List<HRegionInfo> getOnlineRegions() ' HRIs have
tablename. Could figure it client-side
Make sense, will do it in client-side, i have tried with getting a
List<HRegion>, got into serialization issue
bq. Will we have a new dir in zk per cluster region operation we want to do?
Can we not exploit primitives added by hbase-4213? Or do we need to refactor
hbase-4213 to get you primitives you need to do this facility? Or is there
nothing in common w/ what hbase-4213 does (there is at least the closing of a
region?)
We can certainly refactor HBASE-4213 MasterSchemaChangeTracker and
SchemaChangeTracker, we can club them as single tracker on each side (Master
and RS), will dig more.
bq. online merge should have a bunch of overlap w/ this feature? Would be great
if they could share a bunch of code/primitives.
Sure, more refactoring
bq. As has been suggested, rather than a /delete-region, instead we'd have a
log of intent+log of actions thing up in zk I suppose. The log of intent would
list the steps to be done and then the log of actions thingy would log how far
the operation had gone
We are using znode just to start the task and update the state only. If we keep
track of intent vs action in same znode, considering the size of data in znode,
we should not exceed> 1 MB as ZK admin guide says
{panel:title=jute.maxbuffer| borderStyle=dashed| borderColor=#ccc|
titleBGColor=#F7D6C1| bgColor=#FFFFCE}
(Java system property: jute.maxbuffer)
This option can only be set as a Java system property. There is no zookeeper
prefix on it. It specifies the maximum size of the data that can be stored in a
znode. The default is 0xfffff, or just under 1M. If this option is changed, the
system property must be set on all servers and clients otherwise problems will
arise. This is really a sanity check. ZooKeeper is designed to store data on
the order of kilobytes in size.
{panel}
Can we address it in another JIRA as we need to persist znode with Map<Intent,
Action>?
bq.Thats a bit broken in my opinion. Its wonky having zk have reference out to
other main packages. Not your fault. Should have caught that in review of
hbase-4213.
Well, we can still refactor (club schema change trackers and delete-region
trackers into one) and place them into appropriate package?
> Provide capability to delete named region
> -----------------------------------------
>
> Key: HBASE-4991
> URL: https://issues.apache.org/jira/browse/HBASE-4991
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
> Assignee: Mubarak Seyed
> Fix For: 0.94.0
>
> Attachments: HBASE-4991.trunk.v1.patch, HBASE-4991.trunk.v2.patch
>
>
> See discussion titled 'Able to control routing to Solr shards or not' on
> lily-discuss
> User may want to quickly dispose of out of date records by deleting specific
> regions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
