[jira] [Updated] (HBASE-6226) move DataBlockEncoding and related classes to hbase-common module

[ https://issues.apache.org/jira/browse/HBASE-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6226: - Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) I ran the

[jira] [Created] (HBASE-6316) Confirm can upgrade from 0.96 from 0.94 by just stopping and restarting

stack created HBASE-6316: Summary: Confirm can upgrade from 0.96 from 0.94 by just stopping and restarting Key: HBASE-6316 URL: https://issues.apache.org/jira/browse/HBASE-6316 Project: HBase Issue

[jira] [Commented] (HBASE-6294) Detect leftover data in ZK after a user delete all its HBase data

[ https://issues.apache.org/jira/browse/HBASE-6294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13405945#comment-13405945 ] stack commented on HBASE-6294: -- Thats a bug Lars. Aim is to just stop/start to move 0.94 to

[jira] [Commented] (HBASE-6293) HMaster does not go down while splitting logs even if explicit shutdown is called.

[ https://issues.apache.org/jira/browse/HBASE-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13405991#comment-13405991 ] stack commented on HBASE-6293: -- +1 HMaster does not go down while splitting

[jira] [Updated] (HBASE-6039) Remove HMasterInterface and replace with something similar to RegionServerStatusProtocol

[ https://issues.apache.org/jira/browse/HBASE-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6039: - Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Committed to

[jira] [Commented] (HBASE-6134) Improvement for split-worker to speed up distributed log splitting

[ https://issues.apache.org/jira/browse/HBASE-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406014#comment-13406014 ] stack commented on HBASE-6134: -- The patch did not make it into 0.92 and 0.94? Is it supposed

[jira] [Commented] (HBASE-6134) Improvement for split-worker to speed up distributed log splitting

[ https://issues.apache.org/jira/browse/HBASE-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406017#comment-13406017 ] stack commented on HBASE-6134: -- @Ram or @Chunhui You fellas remember an issue that moves a

[jira] [Commented] (HBASE-6117) Revisit default condition added to Switch cases in Trunk

[ https://issues.apache.org/jira/browse/HBASE-6117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406028#comment-13406028 ] stack commented on HBASE-6117: -- +1 on patch minus the redundant logging.

[jira] [Updated] (HBASE-6145) Fix site target post modularization

[ https://issues.apache.org/jira/browse/HBASE-6145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6145: - Resolution: Fixed Fix Version/s: 0.96.0 Hadoop Flags: Reviewed Status: Resolved (was:

[jira] [Commented] (HBASE-6320) assembly:single doesn't work after modularization

[ https://issues.apache.org/jira/browse/HBASE-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406099#comment-13406099 ] stack commented on HBASE-6320: -- bq. I think we should make assembly:single work. You can't

[jira] [Commented] (HBASE-6320) assembly:single doesn't work after modularization

[ https://issues.apache.org/jira/browse/HBASE-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406104#comment-13406104 ] stack commented on HBASE-6320: -- I updated the wiki page to point at refguide. If you think

[jira] [Commented] (HBASE-6272) In-memory region state is inconsistent

[ https://issues.apache.org/jira/browse/HBASE-6272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406110#comment-13406110 ] stack commented on HBASE-6272: -- I added up some comments on RB Jimmy.

[jira] [Commented] (HBASE-6134) Improvement for split-worker to speed up distributed log splitting

[ https://issues.apache.org/jira/browse/HBASE-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406299#comment-13406299 ] stack commented on HBASE-6134: -- Ok. Then it was a pigment of my emancipation that you had.

[jira] [Commented] (HBASE-6283) [region_mover.rb] Add option to exclude list of hosts on unload instead of just assuming the source node.

[ https://issues.apache.org/jira/browse/HBASE-6283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406301#comment-13406301 ] stack commented on HBASE-6283: -- bq. Thanks for the pointer to Aravind's work – this is the

[jira] [Commented] (HBASE-6299) RS starts region open while fails ack to HMaster.sendRegionOpen() causes inconsistency in HMaster's region state and a series of successive problems.

[ https://issues.apache.org/jira/browse/HBASE-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406305#comment-13406305 ] stack commented on HBASE-6299: -- It looks to me like we have same issue in trunk. Your

[jira] [Commented] (HBASE-6326) Nested retry loops in HConnectionManager

[ https://issues.apache.org/jira/browse/HBASE-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406308#comment-13406308 ] stack commented on HBASE-6326: -- +1 Simple but ugly. Good enough for a 0.94.1.

[jira] [Commented] (HBASE-6309) [MTTR] Do NN operations outside of the ZK EventThread in SplitLogManager

[ https://issues.apache.org/jira/browse/HBASE-6309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406310#comment-13406310 ] stack commented on HBASE-6309: -- @Chunhui What about case where we fail a log splitting... how

[jira] [Commented] (HBASE-5450) Support for wire-compatibility in inter-cluster replication (ZK, etc)

[ https://issues.apache.org/jira/browse/HBASE-5450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406315#comment-13406315 ] stack commented on HBASE-5450: -- @Chris See HBASE-5965. Looks like I abandoned it on the last

[jira] [Commented] (HBASE-6309) [MTTR] Do NN operations outside of the ZK EventThread in SplitLogManager

[ https://issues.apache.org/jira/browse/HBASE-6309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406345#comment-13406345 ] stack commented on HBASE-6309: -- What about the logic in moveRecoveredEditsFromTemp? It flags

[jira] [Commented] (HBASE-6299) RS starts region open while fails ack to HMaster.sendRegionOpen() causes inconsistency in HMaster's region state and a series of successive problems.

[ https://issues.apache.org/jira/browse/HBASE-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406533#comment-13406533 ] stack commented on HBASE-6299: -- bq. This piece of code is correct. If we directly check

[jira] [Commented] (HBASE-6319) ReplicationSource can call terminate on itself and deadlock

[ https://issues.apache.org/jira/browse/HBASE-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406539#comment-13406539 ] stack commented on HBASE-6319: -- How does 'this' get shutdown then?

[jira] [Commented] (HBASE-5705) Introduce Protocol Buffer RPC engine

[ https://issues.apache.org/jira/browse/HBASE-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406557#comment-13406557 ] stack commented on HBASE-5705: -- I added some comments up in RB. Seems like pb stuff goes via

[jira] [Commented] (HBASE-6325) [replication] Race in ReplicationSourceManager.init can initiate a failover even if the node is alive

[ https://issues.apache.org/jira/browse/HBASE-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406562#comment-13406562 ] stack commented on HBASE-6325: -- Below returns true if we added regionservers. What if we are

[jira] [Updated] (HBASE-6322) Unnecessary creation of finalizers in HTablePool

[ https://issues.apache.org/jira/browse/HBASE-6322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6322: - Attachment: HBASE-6322-trunk.1.patch What I applied to trunk. Unnecessary creation of

[jira] [Resolved] (HBASE-6322) Unnecessary creation of finalizers in HTablePool

[ https://issues.apache.org/jira/browse/HBASE-6322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-6322. -- Resolution: Fixed Fix Version/s: 0.92.2 Hadoop Flags: Reviewed Applied to 0.92. Thanks for the

[jira] [Updated] (HBASE-6281) Assignment need not be called for disabling table regions during clean cluster start up.

[ https://issues.apache.org/jira/browse/HBASE-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6281: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to 0.92. Thanks for patch Rajesh.

[jira] [Commented] (HBASE-6281) Assignment need not be called for disabling table regions during clean cluster start up.

[ https://issues.apache.org/jira/browse/HBASE-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406711#comment-13406711 ] stack commented on HBASE-6281: -- Added the addendum. Thanks Rajesh.

[jira] [Commented] (HBASE-6283) [region_mover.rb] Add option to exclude list of hosts on unload instead of just assuming the source node.

[ https://issues.apache.org/jira/browse/HBASE-6283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406712#comment-13406712 ] stack commented on HBASE-6283: -- Other versions, yes. Aravind doesn't work on this stuff any

[jira] [Commented] (HBASE-6228) Fixup daughters twice cause daughter region assigned twice

[ https://issues.apache.org/jira/browse/HBASE-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406715#comment-13406715 ] stack commented on HBASE-6228: -- I've been looking at hbase-6060 as a background task (sorry,

[jira] [Updated] (HBASE-6296) Refactor EventType to track its own ExecutorService type

[ https://issues.apache.org/jira/browse/HBASE-6296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6296: - Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Committed to

[jira] [Commented] (HBASE-6228) Fixup daughters twice cause daughter region assigned twice

[ https://issues.apache.org/jira/browse/HBASE-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406753#comment-13406753 ] stack commented on HBASE-6228: -- For example, on study: + RegionState is unreliable figuring

[jira] [Commented] (HBASE-6328) FSHDFSUtils#recoverFileLease tries to rethrow InterruptedException but actually shallows it

[ https://issues.apache.org/jira/browse/HBASE-6328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406755#comment-13406755 ] stack commented on HBASE-6328: -- +1 on patch. Apply it to all branches I'd say Nicolas.

[jira] [Commented] (HBASE-6322) Unnecessary creation of finalizers in HTablePool

[ https://issues.apache.org/jira/browse/HBASE-6322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406760#comment-13406760 ] stack commented on HBASE-6322: -- Thanks Ted. I reverted the patch for now. Thank your time

[jira] [Commented] (HBASE-6288) In hbase-daemons.sh, description of the default backup-master file path is wrong

[ https://issues.apache.org/jira/browse/HBASE-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406767#comment-13406767 ] stack commented on HBASE-6288: -- Sounds right Benjamin. Can you make a patch w/ your fix?

[jira] [Commented] (HBASE-6299) RS starts region open while fails ack to HMaster.sendRegionOpen() causes inconsistency in HMaster's region state and a series of successive problems.

[ https://issues.apache.org/jira/browse/HBASE-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406888#comment-13406888 ] stack commented on HBASE-6299: -- You are right Ram. Good one. So we should not set

[jira] [Commented] (HBASE-6299) RS starts region open while fails ack to HMaster.sendRegionOpen() causes inconsistency in HMaster's region state and a series of successive problems.

[ https://issues.apache.org/jira/browse/HBASE-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13407100#comment-13407100 ] stack commented on HBASE-6299: -- Retries shouldn't do that code path. Dont' you think? We

[jira] [Commented] (HBASE-6175) TestFSUtils flaky on hdfs getFileStatus method

[ https://issues.apache.org/jira/browse/HBASE-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13407149#comment-13407149 ] stack commented on HBASE-6175: -- Is the loop right the way it sets ok = true at the top of the

[jira] [Commented] (HBASE-6175) TestFSUtils flaky on hdfs getFileStatus method

[ https://issues.apache.org/jira/browse/HBASE-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13407161#comment-13407161 ] stack commented on HBASE-6175: -- Don't worry about it; none of my comments are substantial

[jira] [Commented] (HBASE-6060) Regions's in OPENING state from failed regionservers takes a long time to recover

[ https://issues.apache.org/jira/browse/HBASE-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13407482#comment-13407482 ] stack commented on HBASE-6060: -- @Ram Yes. I put something for discussion up in RB:

[jira] [Commented] (HBASE-6318) SplitLogWorker exited due to ConcurrentModificationException

[ https://issues.apache.org/jira/browse/HBASE-6318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13407502#comment-13407502 ] stack commented on HBASE-6318: -- bq. Testing in real cluster is appreciated. ... but not

[jira] [Commented] (HBASE-5909) SlabStats should be a daemon thread

[ https://issues.apache.org/jira/browse/HBASE-5909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13407504#comment-13407504 ] stack commented on HBASE-5909: -- +1 SlabStats should be a daemon thread

[jira] [Commented] (HBASE-6299) RS starts region open while fails ack to HMaster.sendRegionOpen() causes inconsistency in HMaster's region state and a series of successive problems.

[ https://issues.apache.org/jira/browse/HBASE-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13407513#comment-13407513 ] stack commented on HBASE-6299: -- Whatever you think Maryann. I can see us checking the znode

[jira] [Commented] (HBASE-6060) Regions's in OPENING state from failed regionservers takes a long time to recover

[ https://issues.apache.org/jira/browse/HBASE-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13407748#comment-13407748 ] stack commented on HBASE-6060: -- @Lars Yes. @Ted My fault. See

[jira] [Commented] (HBASE-6325) [replication] Race in ReplicationSourceManager.init can initiate a failover even if the node is alive

[ https://issues.apache.org/jira/browse/HBASE-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13407750#comment-13407750 ] stack commented on HBASE-6325: -- On first item, yeah, could be clearer. OK on the second

[jira] [Commented] (HBASE-6060) Regions's in OPENING state from failed regionservers takes a long time to recover

[ https://issues.apache.org/jira/browse/HBASE-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408242#comment-13408242 ] stack commented on HBASE-6060: -- @Ram Good one. Will refresh patch up in RB. Otherwise, do

[jira] [Commented] (HBASE-6060) Regions's in OPENING state from failed regionservers takes a long time to recover

[ https://issues.apache.org/jira/browse/HBASE-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408322#comment-13408322 ] stack commented on HBASE-6060: -- I added update up on RB to address Ted and Ram comments.

[jira] [Commented] (HBASE-6341) Publicly expose HConnectionKey

[ https://issues.apache.org/jira/browse/HBASE-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408334#comment-13408334 ] stack commented on HBASE-6341: -- @Micah Tell us more about your need. This is ugly internals.

[jira] [Commented] (HBASE-6307) Fix hbase hadoop 2.0/0.23 tests

[ https://issues.apache.org/jira/browse/HBASE-6307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408335#comment-13408335 ] stack commented on HBASE-6307: -- Are we supporting 0.23 anymore? How abouts 1.0 and 2.0 only?

[jira] [Commented] (HBASE-6334) TestImprovement for TestHRegion.testWritesWhileGetting

[ https://issues.apache.org/jira/browse/HBASE-6334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408336#comment-13408336 ] stack commented on HBASE-6334: -- You teasing or a patch is coming Gregory?

[jira] [Commented] (HBASE-6337) [MTTR] Remove renaming tmp log file in SplitLogManager

[ https://issues.apache.org/jira/browse/HBASE-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408344#comment-13408344 ] stack commented on HBASE-6337: -- If you are removing tmp dir, don't be half-hearted about it.

[jira] [Commented] (HBASE-6220) PersistentMetricsTimeVaryingRate gets used for non-time-based metrics

[ https://issues.apache.org/jira/browse/HBASE-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408347#comment-13408347 ] stack commented on HBASE-6220: -- Did Elliott's question of Paul get answered? i.e. if the

[jira] [Commented] (HBASE-3855) Performance degradation of memstore because reseek is linear

[ https://issues.apache.org/jira/browse/HBASE-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408374#comment-13408374 ] stack commented on HBASE-3855: -- Thanks Gregory. Kick your Jon. He might be interested in

[jira] [Resolved] (HBASE-6341) Publicly expose HConnectionKey

[ https://issues.apache.org/jira/browse/HBASE-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-6341. -- Resolution: Fixed Fix Version/s: 0.94.1 0.92.2 Hadoop Flags: Reviewed Committed

[jira] [Commented] (HBASE-6333) MemStoreScanner {kvsetAtCreation,snapshotAtCreation} should be private and not volatile

[ https://issues.apache.org/jira/browse/HBASE-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408386#comment-13408386 ] stack commented on HBASE-6333: -- +1 on patch did it get committed? (If set only on

[jira] [Commented] (HBASE-6060) Regions's in OPENING state from failed regionservers takes a long time to recover

[ https://issues.apache.org/jira/browse/HBASE-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408404#comment-13408404 ] stack commented on HBASE-6060: -- I can fix that. But I just thought of something; the way I'm

[jira] [Updated] (HBASE-6333) MemStoreScanner {kvsetAtCreation,snapshotAtCreation} should be private and not volatile

[ https://issues.apache.org/jira/browse/HBASE-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6333: - Resolution: Fixed Fix Version/s: 0.96.0 Hadoop Flags: Reviewed Status: Resolved (was:

[jira] [Commented] (HBASE-6325) [replication] Race in ReplicationSourceManager.init can initiate a failover even if the node is alive

[ https://issues.apache.org/jira/browse/HBASE-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408598#comment-13408598 ] stack commented on HBASE-6325: -- +1 [replication] Race in

[jira] [Commented] (HBASE-6060) Regions's in OPENING state from failed regionservers takes a long time to recover

[ https://issues.apache.org/jira/browse/HBASE-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408601#comment-13408601 ] stack commented on HBASE-6060: -- v3 should be good. I posted it up on RB. Addresses Ted and

[jira] [Commented] (HBASE-6307) Fix hbase hadoop 2.0/0.23 tests

[ https://issues.apache.org/jira/browse/HBASE-6307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408618#comment-13408618 ] stack commented on HBASE-6307: -- We should raise it on dev list unless good reason for keeping

[jira] [Commented] (HBASE-6220) PersistentMetricsTimeVaryingRate gets used for non-time-based metrics

[ https://issues.apache.org/jira/browse/HBASE-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408619#comment-13408619 ] stack commented on HBASE-6220: -- @Paul Easy test is browse to /jmx on regionserver. Look for

[jira] [Commented] (HBASE-6205) Support an option to keep data of dropped table for some time

[ https://issues.apache.org/jira/browse/HBASE-6205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408620#comment-13408620 ] stack commented on HBASE-6205: -- bq. Unfortunately, it happens in our environment because one

[jira] [Commented] (HBASE-6352) Add copy method in Bytes

[ https://issues.apache.org/jira/browse/HBASE-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408631#comment-13408631 ] stack commented on HBASE-6352: -- Patch looks good. The formatting is off. No tabs in hbase

[jira] [Commented] (HBASE-6352) Add copy method in Bytes

[ https://issues.apache.org/jira/browse/HBASE-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408722#comment-13408722 ] stack commented on HBASE-6352: -- Patch looks good Jean-Marc. Add copy method

[jira] [Commented] (HBASE-6233) [brainstorm] snapshots: hardlink alternatives

[ https://issues.apache.org/jira/browse/HBASE-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408762#comment-13408762 ] stack commented on HBASE-6233: -- @Matteo Thanks for taking the time to do the writeup.

[jira] [Commented] (HBASE-6233) [brainstorm] snapshots: hardlink alternatives

[ https://issues.apache.org/jira/browse/HBASE-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408771#comment-13408771 ] stack commented on HBASE-6233: -- bq. The time is (fs.rename() * nfiles + fs.symlink() *

[jira] [Commented] (HBASE-5547) Don't delete HFiles when in backup mode

[ https://issues.apache.org/jira/browse/HBASE-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408778#comment-13408778 ] stack commented on HBASE-5547: -- Added some review up on rb. Don't delete

[jira] [Commented] (HBASE-5261) Update HBase for Java 7

[ https://issues.apache.org/jira/browse/HBASE-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408780#comment-13408780 ] stack commented on HBASE-5261: -- Do we need this addition if we are running on jdk7? I'm

[jira] [Commented] (HBASE-5261) Update HBase for Java 7

[ https://issues.apache.org/jira/browse/HBASE-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408870#comment-13408870 ] stack commented on HBASE-5261: -- Above sounds good. What about case where we compile w/ jdk7

[jira] [Commented] (HBASE-5261) Update HBase for Java 7

[ https://issues.apache.org/jira/browse/HBASE-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408871#comment-13408871 ] stack commented on HBASE-5261: -- Hmm... I suppose the -options flag has not effect in this

[jira] [Commented] (HBASE-6329) Stopping META regionserver when splitting region could cause daughter region to be assigned twice

[ https://issues.apache.org/jira/browse/HBASE-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408976#comment-13408976 ] stack commented on HBASE-6329: -- +1. All changes in patch look reasonable to me (we don't have

[jira] [Commented] (HBASE-6354) Wait till hard fail in case of erratic zookeeper session expiry

[ https://issues.apache.org/jira/browse/HBASE-6354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13409018#comment-13409018 ] stack commented on HBASE-6354: -- {code} +final boolean[] isClosed = new boolean[] { false

[jira] [Commented] (HBASE-6233) [brainstorm] snapshots: hardlink alternatives

[ https://issues.apache.org/jira/browse/HBASE-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13409066#comment-13409066 ] stack commented on HBASE-6233: -- Looking at the doc. again: Is there a table dir missing from

[jira] [Commented] (HBASE-6233) [brainstorm] snapshots: hardlink alternatives

[ https://issues.apache.org/jira/browse/HBASE-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13409257#comment-13409257 ] stack commented on HBASE-6233: -- It'd be a radical change Matteo. It feels like a hbase 2.0

[jira] [Updated] (HBASE-6356) printStackTrace in FSUtils

[ https://issues.apache.org/jira/browse/HBASE-6356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6356: - Tags: noob Labels: noob (was: ) printStackTrace in FSUtils --

[jira] [Commented] (HBASE-6356) printStackTrace in FSUtils

[ https://issues.apache.org/jira/browse/HBASE-6356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13409543#comment-13409543 ] stack commented on HBASE-6356: -- I suppose we're not allowed throw in here? Should we throw a

[jira] [Commented] (HBASE-5151) Rename hbase.skip.errors in HRegion as it is too general-sounding.

[ https://issues.apache.org/jira/browse/HBASE-5151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13409551#comment-13409551 ] stack commented on HBASE-5151: -- @Harsh Patch looks good. Does the above test fail for you?

[jira] [Commented] (HBASE-6337) [MTTR] Remove renaming tmp log file in SplitLogManager

[ https://issues.apache.org/jira/browse/HBASE-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13409557#comment-13409557 ] stack commented on HBASE-6337: -- @Lars I'm not sure why it was done originally. Prakash was

[jira] [Commented] (HBASE-6337) [MTTR] Remove renaming tmp log file in SplitLogManager

[ https://issues.apache.org/jira/browse/HBASE-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13409564#comment-13409564 ] stack commented on HBASE-6337: -- @Chunhui The patch looks good. Thanks for all the cleanup.

[jira] [Commented] (HBASE-6060) Regions's in OPENING state from failed regionservers takes a long time to recover

[ https://issues.apache.org/jira/browse/HBASE-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13409749#comment-13409749 ] stack commented on HBASE-6060: -- bq. Do we need to test the perf because now the transition

[jira] [Updated] (HBASE-6060) Regions's in OPENING state from failed regionservers takes a long time to recover

[ https://issues.apache.org/jira/browse/HBASE-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6060: - Fix Version/s: (was: 0.94.1) 0.94.2 This won't be done for 0.94.1 is my guess. Moving it

[jira] [Commented] (HBASE-5997) Fix concerns raised in HBASE-5922 related to HalfStoreFileReader

[ https://issues.apache.org/jira/browse/HBASE-5997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13409794#comment-13409794 ] stack commented on HBASE-5997: -- @Anoop Great work. Agree on the seekBefore finding. Lets

[jira] [Commented] (HBASE-6317) Master clean start up and Partially enabled tables make region assignment inconsistent.

[ https://issues.apache.org/jira/browse/HBASE-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13409822#comment-13409822 ] stack commented on HBASE-6317: -- Does this need to be public? Can it be package private?

[jira] [Commented] (HBASE-6345) Utilize fault injection in testing using AspectJ

[ https://issues.apache.org/jira/browse/HBASE-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13409865#comment-13409865 ] stack commented on HBASE-6345: -- So we should close this issue or redo as 'Fault Injection in

[jira] [Commented] (HBASE-6323) [replication] most of the source metrics are wrong when there's multiple slaves

[ https://issues.apache.org/jira/browse/HBASE-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13409868#comment-13409868 ] stack commented on HBASE-6323: -- Looks good Mr. Elliott. Will give J-D honor of blessing it.

[jira] [Commented] (HBASE-6357) Failed distributed log splitting stuck on master web UI

[ https://issues.apache.org/jira/browse/HBASE-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13409872#comment-13409872 ] stack commented on HBASE-6357: -- +1 and what Ted says (commit if hadoopqa looks reasonable)

[jira] [Commented] (HBASE-6323) [replication] most of the source metrics are wrong when there's multiple slaves

[ https://issues.apache.org/jira/browse/HBASE-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13409881#comment-13409881 ] stack commented on HBASE-6323: -- I'm +1 then. [replication] most of the

[jira] [Commented] (HBASE-5997) Fix concerns raised in HBASE-5922 related to HalfStoreFileReader

[ https://issues.apache.org/jira/browse/HBASE-5997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13410915#comment-13410915 ] stack commented on HBASE-5997: -- @Lars I think you should commit it just because of the amount

[jira] [Commented] (HBASE-6299) RS starts region open while fails ack to HMaster.sendRegionOpen() causes inconsistency in HMaster's region state and a series of successive problems.

[ https://issues.apache.org/jira/browse/HBASE-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13411462#comment-13411462 ] stack commented on HBASE-6299: -- @Mary Is HBASE-5396 committed? bq. We now set RegionState

[jira] [Commented] (HBASE-6299) RS starts region open while fails ack to HMaster.sendRegionOpen() causes inconsistency in HMaster's region state and a series of successive problems.

[ https://issues.apache.org/jira/browse/HBASE-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13411466#comment-13411466 ] stack commented on HBASE-6299: -- bq. I'm not sure what the lock on an encoded name String does

[jira] [Commented] (HBASE-6370) Add compression codec test at HMaster when createTable/modifyColumn/modifyTable

[ https://issues.apache.org/jira/browse/HBASE-6370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13411470#comment-13411470 ] stack commented on HBASE-6370: -- @ShiXing This is a good idea. I think you should be able to

[jira] [Commented] (HBASE-6369) HTable is not closed in AggregationClient

[ https://issues.apache.org/jira/browse/HBASE-6369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13411471#comment-13411471 ] stack commented on HBASE-6369: -- +1 on patch. HTable is not closed in

[jira] [Commented] (HBASE-2730) Expose RS work queue contents on web UI

[ https://issues.apache.org/jira/browse/HBASE-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13411502#comment-13411502 ] stack commented on HBASE-2730: -- +1 on patch. Mind posting sample of what it looks like Jie?

[jira] [Updated] (HBASE-5151) Rename hbase.skip.errors in HRegion as it is too general-sounding.

[ https://issues.apache.org/jira/browse/HBASE-5151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-5151: - Resolution: Fixed Fix Version/s: 0.96.0 Hadoop Flags: Reviewed Status: Resolved (was:

[jira] [Commented] (HBASE-2730) Expose RS work queue contents on web UI

[ https://issues.apache.org/jira/browse/HBASE-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13411513#comment-13411513 ] stack commented on HBASE-2730: -- Does the 29th of June output include output from the patch

[jira] [Commented] (HBASE-3725) HBase increments from old value after delete and write to disk

[ https://issues.apache.org/jira/browse/HBASE-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13411518#comment-13411518 ] stack commented on HBASE-3725: -- @ShiXing I'm reluctant to commit this to 0.92 if it slows

[jira] [Updated] (HBASE-6359) KeyValue may return incorrect values after readFields()

[ https://issues.apache.org/jira/browse/HBASE-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6359: - Tags: noob Labels: noob (was: ) KeyValue may return incorrect values after readFields()

[jira] [Updated] (HBASE-2730) Expose RS work queue contents on web UI

[ https://issues.apache.org/jira/browse/HBASE-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-2730: - Resolution: Fixed Fix Version/s: 0.94.1 Hadoop Flags: Reviewed Status: Resolved (was:

[jira] [Commented] (HBASE-6290) Add a function a mark a server as dead and start the recovery the process

[ https://issues.apache.org/jira/browse/HBASE-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13411545#comment-13411545 ] stack commented on HBASE-6290: -- Sounds good. Add a function a mark a server

[jira] [Updated] (HBASE-6290) Add a function a mark a server as dead and start the recovery the process

[ https://issues.apache.org/jira/browse/HBASE-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6290: - Tags: noob Labels: noob (was: ) Add a function a mark a server as dead and start the recovery the

[jira] [Commented] (HBASE-5151) Rename hbase.skip.errors in HRegion as it is too general-sounding.

[ https://issues.apache.org/jira/browse/HBASE-5151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13411959#comment-13411959 ] stack commented on HBASE-5151: -- @Harsh No need to apologize. Thanks for fast turn around.

<    5   6   7   8   9   10   11   12   13   14   >