[jira] [Commented] (HBASE-5244) Add a test for a column with 1M (10M? 100M) items and see how we do with it

[ https://issues.apache.org/jira/browse/HBASE-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13190542#comment-13190542 ] stack commented on HBASE-5244: -- Lets add a test that fills a row with a million columns and

[jira] [Commented] (HBASE-4920) We need a mascot, a totem

[ https://issues.apache.org/jira/browse/HBASE-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13190777#comment-13190777 ] stack commented on HBASE-4920: -- I like circle. I like the monochormatic take. I wonder if

[jira] [Commented] (HBASE-5237) Addendum for HBASE-5160 and HBASE-4397

[ https://issues.apache.org/jira/browse/HBASE-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13190788#comment-13190788 ] stack commented on HBASE-5237: -- +1 on commit to 0.92 branch so we are consistent with 0.90

[jira] [Commented] (HBASE-5243) LogSyncerThread not getting shutdown waiting for the interrupted flag

[ https://issues.apache.org/jira/browse/HBASE-5243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13190793#comment-13190793 ] stack commented on HBASE-5243: -- +1 for 0.92 branch LogSyncerThread not

[jira] [Commented] (HBASE-5245) HBase shell should use alternate jruby if JRUBY_HOME is set, should pass along JRUBY_OPTS

[ https://issues.apache.org/jira/browse/HBASE-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13190795#comment-13190795 ] stack commented on HBASE-5245: -- I tried apply to TRUNK and it fails. Mind fixing Philip?

[jira] [Commented] (HBASE-5245) HBase shell should use alternate jruby if JRUBY_HOME is set, should pass along JRUBY_OPTS

[ https://issues.apache.org/jira/browse/HBASE-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13190797#comment-13190797 ] stack commented on HBASE-5245: -- Oh, nvm. I see you say why you need this above.

[jira] [Commented] (HBASE-5237) Addendum for HBASE-5160 and HBASE-4397

[ https://issues.apache.org/jira/browse/HBASE-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13190873#comment-13190873 ] stack commented on HBASE-5237: -- Thanks for explanation Ram. This code is hard to follow.

[jira] [Commented] (HBASE-5179) Concurrent processing of processFaileOver and ServerShutdownHandler may cause region to be assigned before log splitting is completed, causing data loss

[ https://issues.apache.org/jira/browse/HBASE-5179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13190894#comment-13190894 ] stack commented on HBASE-5179: -- Here is some review of v17. logDirExists should be called

[jira] [Commented] (HBASE-5229) Explore building blocks for multi-row local transactions.

[ https://issues.apache.org/jira/browse/HBASE-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13190898#comment-13190898 ] stack commented on HBASE-5229: -- In the above when you talk of column prefix, couldn't that be

[jira] [Commented] (HBASE-5229) Explore building blocks for multi-row local transactions.

[ https://issues.apache.org/jira/browse/HBASE-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13190897#comment-13190897 ] stack commented on HBASE-5229: -- In the above when you talk of column prefix, couldn't that be

[jira] [Commented] (HBASE-5231) Backport HBASE-3373 (per-table load balancing) to 0.92

[ https://issues.apache.org/jira/browse/HBASE-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13191377#comment-13191377 ] stack commented on HBASE-5231: -- It looks like a method named getAssignmentsByTable will only

[jira] [Commented] (HBASE-5255) Use singletons for OperationStatus to save memory

[ https://issues.apache.org/jira/browse/HBASE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13191919#comment-13191919 ] stack commented on HBASE-5255: -- +1 on patch Use singletons for

[jira] [Commented] (HBASE-5189) Add metrics to keep track of region-splits in RS

[ https://issues.apache.org/jira/browse/HBASE-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13191920#comment-13191920 ] stack commented on HBASE-5189: -- +1 Add metrics to keep track of

[jira] [Commented] (HBASE-5229) Explore building blocks for multi-row local transactions.

[ https://issues.apache.org/jira/browse/HBASE-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13191927#comment-13191927 ] stack commented on HBASE-5229: -- I see now what the other delete issue is about. Regards CF

[jira] [Commented] (HBASE-5262) Structured event log for HBase for monitoring and auto-tuning performance

[ https://issues.apache.org/jira/browse/HBASE-5262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13191933#comment-13191933 ] stack commented on HBASE-5262: -- @Mikhail Sounds good. We'd write to hbase because we can't

[jira] [Commented] (HBASE-5179) Concurrent processing of processFaileOver and ServerShutdownHandler may cause region to be assigned before log splitting is completed, causing data loss

[ https://issues.apache.org/jira/browse/HBASE-5179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13191954#comment-13191954 ] stack commented on HBASE-5179: -- Reviewing 0.92v17 isDeadServerInProgress is a new public

[jira] [Commented] (HBASE-5230) Unit test to ensure compactions don't cache data on write

[ https://issues.apache.org/jira/browse/HBASE-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13191959#comment-13191959 ] stack commented on HBASE-5230: -- lgtm Unit test to ensure compactions don't

[jira] [Commented] (HBASE-5231) Backport HBASE-3373 (per-table load balancing) to 0.92

[ https://issues.apache.org/jira/browse/HBASE-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13191971#comment-13191971 ] stack commented on HBASE-5231: -- That the methods are package private is not relevant. My

[jira] [Commented] (HBASE-5269) IllegalMonitorStateException while retryin HLog split in 0.90 branch.

[ https://issues.apache.org/jira/browse/HBASE-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13192248#comment-13192248 ] stack commented on HBASE-5269: -- +1 IllegalMonitorStateException while

[jira] [Commented] (HBASE-5231) Backport HBASE-3373 (per-table load balancing) to 0.92

[ https://issues.apache.org/jira/browse/HBASE-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13192251#comment-13192251 ] stack commented on HBASE-5231: -- It does not necessarily by table; could be by server. Whats

[jira] [Commented] (HBASE-5262) Structured event log for HBase for monitoring and auto-tuning performance

[ https://issues.apache.org/jira/browse/HBASE-5262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13192253#comment-13192253 ] stack commented on HBASE-5262: -- @Mikhail Sounds good to me Structured event

[jira] [Commented] (HBASE-5267) Add a configuration to disable the slab cache by default

[ https://issues.apache.org/jira/browse/HBASE-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13192257#comment-13192257 ] stack commented on HBASE-5267: -- lgtm Add a configuration to disable the

[jira] [Commented] (HBASE-5204) Backward compatibility fixes for 0.92

[ https://issues.apache.org/jira/browse/HBASE-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13192267#comment-13192267 ] stack commented on HBASE-5204: -- Yes, agree, adding patch to trunk would be silly. Lets drop

[jira] [Commented] (HBASE-5231) Backport HBASE-3373 (per-table load balancing) to 0.92

[ https://issues.apache.org/jira/browse/HBASE-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13192372#comment-13192372 ] stack commented on HBASE-5231: -- Its unexplained in the code, its just introduced and its very

[jira] [Commented] (HBASE-5231) Backport HBASE-3373 (per-table load balancing) to 0.92

[ https://issues.apache.org/jira/browse/HBASE-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13192440#comment-13192440 ] stack commented on HBASE-5231: -- In a method named getAssignmentsByTable we will return

[jira] [Commented] (HBASE-5262) Structured event log for HBase for monitoring and auto-tuning performance

[ https://issues.apache.org/jira/browse/HBASE-5262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13192603#comment-13192603 ] stack commented on HBASE-5262: -- @Mikhail We used have an extra column family in .META. called

[jira] [Commented] (HBASE-5231) Backport HBASE-3373 (per-table load balancing) to 0.92

[ https://issues.apache.org/jira/browse/HBASE-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13192612#comment-13192612 ] stack commented on HBASE-5231: -- bq. The relationship between this feature and balancer

[jira] [Commented] (HBASE-5249) Using a stale explicit row lock in a Put triggers an NPE

[ https://issues.apache.org/jira/browse/HBASE-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13192635#comment-13192635 ] stack commented on HBASE-5249: -- Copying over Ted comment that was in hbase-5171 (resolved as

[jira] [Commented] (HBASE-5270) Handle potential data loss due to concurrent processing of processFaileOver and ServerShutdownHandler

[ https://issues.apache.org/jira/browse/HBASE-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13193187#comment-13193187 ] stack commented on HBASE-5270: -- bq. So, the param 'definitiveRootServer' is used in this case

[jira] [Commented] (HBASE-5270) Handle potential data loss due to concurrent processing of processFaileOver and ServerShutdownHandler

[ https://issues.apache.org/jira/browse/HBASE-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13193209#comment-13193209 ] stack commented on HBASE-5270: -- bq. What if the region server hosting .META. went down ?

[jira] [Commented] (HBASE-5276) PerformanceEvaluation does not set the correct classpath for MR because it lives in the test jar

[ https://issues.apache.org/jira/browse/HBASE-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13193255#comment-13193255 ] stack commented on HBASE-5276: -- @Tim Maybe open issue against CDH and close this one?

[jira] [Commented] (HBASE-5278) HBase shell script refers to removed migrate functionality

[ https://issues.apache.org/jira/browse/HBASE-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13193365#comment-13193365 ] stack commented on HBASE-5278: -- @Jon I've a bit of practise HBase shell

[jira] [Commented] (HBASE-5279) NPE in Master after upgrading to 0.92.0

[ https://issues.apache.org/jira/browse/HBASE-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13193363#comment-13193363 ] stack commented on HBASE-5279: -- Skipping should be fine. You have a scan of .META. from

[jira] [Commented] (HBASE-4991) Provide capability to delete named region

[ https://issues.apache.org/jira/browse/HBASE-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13195136#comment-13195136 ] stack commented on HBASE-4991: -- bq. For successive regions R1, R2 and R3, if we delete R2, we

[jira] [Commented] (HBASE-5120) Timeout monitor races with table disable handler

[ https://issues.apache.org/jira/browse/HBASE-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13195163#comment-13195163 ] stack commented on HBASE-5120: -- So, setting down the TM period from 30 minutes to 2 minutes

[jira] [Commented] (HBASE-5229) Explore building blocks for multi-row local transactions.

[ https://issues.apache.org/jira/browse/HBASE-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13195187#comment-13195187 ] stack commented on HBASE-5229: -- @Lars I'm 'intellectually' interested. I have no practical

[jira] [Commented] (HBASE-3134) [replication] Add the ability to enable/disable streams

[ https://issues.apache.org/jira/browse/HBASE-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13195189#comment-13195189 ] stack commented on HBASE-3134: -- bq. Should I do this in this ticket or file another issue?

[jira] [Commented] (HBASE-4810) Clean up IPC logging configuration

[ https://issues.apache.org/jira/browse/HBASE-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197029#comment-13197029 ] stack commented on HBASE-4810: -- +1 Clean up IPC logging configuration

[jira] [Commented] (HBASE-5285) runtime exception -- cached an already cached block -- during compaction

[ https://issues.apache.org/jira/browse/HBASE-5285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197311#comment-13197311 ] stack commented on HBASE-5285: -- Can you make this happen reliably Simon?

[jira] [Commented] (HBASE-5286) bin/hbase's logic of adding Hadoop jar files to the classpath is fragile when presented with split packaged Hadoop 0.23 installation

[ https://issues.apache.org/jira/browse/HBASE-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197316#comment-13197316 ] stack commented on HBASE-5286: -- Thanks for filing the issue Roman.

[jira] [Commented] (HBASE-5229) Explore building blocks for multi-row local transactions.

[ https://issues.apache.org/jira/browse/HBASE-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197328#comment-13197328 ] stack commented on HBASE-5229: -- bq. I hear you. Means that the client and data modeling would

[jira] [Commented] (HBASE-5268) Add delete column prefix delete marker

[ https://issues.apache.org/jira/browse/HBASE-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197340#comment-13197340 ] stack commented on HBASE-5268: -- I added a footnote to book in delete section pointing at your

[jira] [Commented] (HBASE-5266) Add documentation for ColumnRangeFilter

[ https://issues.apache.org/jira/browse/HBASE-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197347#comment-13197347 ] stack commented on HBASE-5266: -- Nothing wrong w/ your english. The below needs a bit more

[jira] [Commented] (HBASE-5281) Should a failure in creating an unassigned node abort the master?

[ https://issues.apache.org/jira/browse/HBASE-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197359#comment-13197359 ] stack commented on HBASE-5281: -- I'm not sure removing the abort only is enough Harsh. If we

[jira] [Commented] (HBASE-5299) CatalogTracker.getMetaServerConnection() checks for root server connection and makes waitForMeta to go into infinite loop in region assignment flow.

[ https://issues.apache.org/jira/browse/HBASE-5299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197362#comment-13197362 ] stack commented on HBASE-5299: -- I could take this one Ram. I'm trying to hack up testing

[jira] [Commented] (HBASE-5280) Remove AssignmentManager#clearRegionFromTransition and replace with assignmentManager#regionOffline

[ https://issues.apache.org/jira/browse/HBASE-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197373#comment-13197373 ] stack commented on HBASE-5280: -- +1 Remove

[jira] [Commented] (HBASE-5309) Hbase web-app /jmx throws an exception

[ https://issues.apache.org/jira/browse/HBASE-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197393#comment-13197393 ] stack commented on HBASE-5309: -- If you go to /jmx, are we supposed to dump a view on jmx?

[jira] [Commented] (HBASE-3850) Log more details when a scanner lease expires

[ https://issues.apache.org/jira/browse/HBASE-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197392#comment-13197392 ] stack commented on HBASE-3850: -- +1 on patch (fix spacing on the 'else' on commit) Won't

[jira] [Commented] (HBASE-3859) Increment a counter when a Scanner lease expires

[ https://issues.apache.org/jira/browse/HBASE-3859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197395#comment-13197395 ] stack commented on HBASE-3859: -- Patch looks good. Any evidence it works Mubarak?

[jira] [Commented] (HBASE-5283) Request counters may become negative for heavily loaded regions

[ https://issues.apache.org/jira/browse/HBASE-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197398#comment-13197398 ] stack commented on HBASE-5283: -- +1 on patch. Request counters may become

[jira] [Commented] (HBASE-5283) Request counters may become negative for heavily loaded regions

[ https://issues.apache.org/jira/browse/HBASE-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197400#comment-13197400 ] stack commented on HBASE-5283: -- +1 on patch. Request counters may become

[jira] [Commented] (HBASE-5281) Should a failure in creating an unassigned node abort the master?

[ https://issues.apache.org/jira/browse/HBASE-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197445#comment-13197445 ] stack commented on HBASE-5281: -- At least in 0.92.0 (and 0.89fb) we are using recoverablezk.

[jira] [Commented] (HBASE-5256) Use WritableUtils.readVInt() in RegionLoad.readFields()

[ https://issues.apache.org/jira/browse/HBASE-5256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197475#comment-13197475 ] stack commented on HBASE-5256: -- Will we have to be careful with this patch? It can't go into

[jira] [Commented] (HBASE-5256) Use WritableUtils.readVInt() in RegionLoad.readFields()

[ https://issues.apache.org/jira/browse/HBASE-5256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197586#comment-13197586 ] stack commented on HBASE-5256: -- Yes. Upgrading. Seems like it'd be easy to make this

[jira] [Commented] (HBASE-5309) Hbase web-app /jmx throws an exception

[ https://issues.apache.org/jira/browse/HBASE-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197587#comment-13197587 ] stack commented on HBASE-5309: -- That'd work for us. Hbase web-app /jmx

[jira] [Commented] (HBASE-1621) merge tool should work on online cluster, but disabled table

[ https://issues.apache.org/jira/browse/HBASE-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197942#comment-13197942 ] stack commented on HBASE-1621: -- Would you mind uploading a version of online_merge.rb w/

[jira] [Commented] (HBASE-5314) Gracefully rolling restart region servers in rolling-restart.sh

[ https://issues.apache.org/jira/browse/HBASE-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13198024#comment-13198024 ] stack commented on HBASE-5314: -- This is interesting. You are putting together

[jira] [Commented] (HBASE-5286) bin/hbase's logic of adding Hadoop jar files to the classpath is fragile when presented with split packaged Hadoop 0.23 installation

[ https://issues.apache.org/jira/browse/HBASE-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13198037#comment-13198037 ] stack commented on HBASE-5286: -- Why do they have to be in a different dir? Can't we do some

[jira] [Commented] (HBASE-3792) TableInputFormat leaks ZK connections

[ https://issues.apache.org/jira/browse/HBASE-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13199528#comment-13199528 ] stack commented on HBASE-3792: -- @Bryan Yes please. Thats crazy acrobatics you are at just to

[jira] [Commented] (HBASE-5325) Expose basic information about the master-status through jmx beans

[ https://issues.apache.org/jira/browse/HBASE-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13199534#comment-13199534 ] stack commented on HBASE-5325: -- bq. Similar to the Namenode and Jobtracker, it would be good

[jira] [Commented] (HBASE-5325) Expose basic information about the master-status through jmx beans

[ https://issues.apache.org/jira/browse/HBASE-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13199542#comment-13199542 ] stack commented on HBASE-5325: -- Can the bean implementation be outside of the master? Just

[jira] [Commented] (HBASE-5318) Support Eclipse Indigo

[ https://issues.apache.org/jira/browse/HBASE-5318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13199545#comment-13199545 ] stack commented on HBASE-5318: -- Should this get a bit of doc in the reference guide? Around

[jira] [Commented] (HBASE-4336) Convert source tree into maven modules

[ https://issues.apache.org/jira/browse/HBASE-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13199551#comment-13199551 ] stack commented on HBASE-4336: -- @Jesse For this kind of work I'd suggest something like

[jira] [Commented] (HBASE-5328) Small changes to Master to make it more testable

[ https://issues.apache.org/jira/browse/HBASE-5328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13199888#comment-13199888 ] stack commented on HBASE-5328: -- bq. I think MockRegionServer.java should be placed under

[jira] [Commented] (HBASE-5318) Support Eclipse Indigo

[ https://issues.apache.org/jira/browse/HBASE-5318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13200014#comment-13200014 ] stack commented on HBASE-5318: -- That looks like CLASSPATH messup where hadoop jar is now

[jira] [Commented] (HBASE-5341) HBase build artifact should include security code by defult

[ https://issues.apache.org/jira/browse/HBASE-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13202103#comment-13202103 ] stack commented on HBASE-5341: -- bq. This would break the ability to compile HBase 0.92+

[jira] [Commented] (HBASE-5325) Expose basic information about the master-status through jmx beans

[ https://issues.apache.org/jira/browse/HBASE-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13202108#comment-13202108 ] stack commented on HBASE-5325: -- @Enis metrics2 seems a bit out there for us (hadoop 0.23?).

[jira] [Commented] (HBASE-5347) GC free memory management in Level-1 Block Cache

[ https://issues.apache.org/jira/browse/HBASE-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13202898#comment-13202898 ] stack commented on HBASE-5347: -- Very nice idea (if the reference counting can be figured).

[jira] [Commented] (HBASE-5341) HBase build artifact should include security code by defult

[ https://issues.apache.org/jira/browse/HBASE-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13202908#comment-13202908 ] stack commented on HBASE-5341: -- @Enis 0.92 won't be modularized. HBASE-5288 will be fixed in

[jira] [Commented] (HBASE-5348) Constraint configuration loaded with bloat

[ https://issues.apache.org/jira/browse/HBASE-5348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13202916#comment-13202916 ] stack commented on HBASE-5348: -- Why don't you want to load the 'default' config? What do you

[jira] [Commented] (HBASE-5347) GC free memory management in Level-1 Block Cache

[ https://issues.apache.org/jira/browse/HBASE-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13202919#comment-13202919 ] stack commented on HBASE-5347: -- Blocks are not all of the same size. Will this be an issue?

[jira] [Commented] (HBASE-5348) Constraint configuration loaded with bloat

[ https://issues.apache.org/jira/browse/HBASE-5348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13202946#comment-13202946 ] stack commented on HBASE-5348: -- @Jesse Ok. Make a patch w/ the little paragraph as a comment

[jira] [Commented] (HBASE-5341) HBase build artifact should include security code by defult

[ https://issues.apache.org/jira/browse/HBASE-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13202951#comment-13202951 ] stack commented on HBASE-5341: -- Will do. Let me peg this issue against 0.92.1 so we don't

[jira] [Commented] (HBASE-5350) Fix jamon generated package names

[ https://issues.apache.org/jira/browse/HBASE-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13202966#comment-13202966 ] stack commented on HBASE-5350: -- If you run hbase, the webui comes up fine? Otherwise patch

[jira] [Commented] (HBASE-5348) Constraint configuration loaded with bloat

[ https://issues.apache.org/jira/browse/HBASE-5348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13202971#comment-13202971 ] stack commented on HBASE-5348: -- I see that now. Agree it would be overkill. Let me commit.

[jira] [Commented] (HBASE-5346) Fix testColumnFamilyCompression and test_TIMERANGE in TestHFileOutputFormat

[ https://issues.apache.org/jira/browse/HBASE-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13202986#comment-13202986 ] stack commented on HBASE-5346: -- Patch looks good to me. Let me submit the patch to see if it

[jira] [Commented] (HBASE-5335) Dynamic Schema Configurations

[ https://issues.apache.org/jira/browse/HBASE-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13203114#comment-13203114 ] stack commented on HBASE-5335: -- bq. Combined with online schema change, this will allow us to

[jira] [Commented] (HBASE-5221) bin/hbase script doesn't look for Hadoop jars in the right place in trunk layout

[ https://issues.apache.org/jira/browse/HBASE-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13203273#comment-13203273 ] stack commented on HBASE-5221: -- So idea is to put hadoop jars under /share? Where does this

[jira] [Commented] (HBASE-5335) Dynamic Schema Configurations

[ https://issues.apache.org/jira/browse/HBASE-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13203269#comment-13203269 ] stack commented on HBASE-5335: -- bq ...but you'd need to do a large refactor to handle truly

[jira] [Commented] (HBASE-5292) getsize per-CF metric incorrectly counts compaction related reads as well

[ https://issues.apache.org/jira/browse/HBASE-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13203277#comment-13203277 ] stack commented on HBASE-5292: -- This patch is for trunk? You going to commit Mikhail? Seems

[jira] [Commented] (HBASE-5336) Spurious exceptions in HConnectionImplementation

[ https://issues.apache.org/jira/browse/HBASE-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13203314#comment-13203314 ] stack commented on HBASE-5336: -- Are we calling a sync before a new WAL initialized?

[jira] [Commented] (HBASE-5221) bin/hbase script doesn't look for Hadoop jars in the right place in trunk layout

[ https://issues.apache.org/jira/browse/HBASE-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13203687#comment-13203687 ] stack commented on HBASE-5221: -- No worries Jimmy. That'll do. Thanks. Let me commit.

[jira] [Commented] (HBASE-3537) [site] Make it so each page of manual allows users comment like mysql's manual does

[ https://issues.apache.org/jira/browse/HBASE-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13203785#comment-13203785 ] stack commented on HBASE-3537: -- I don't seem to have filled in here that I couldn't figure

[jira] [Commented] (HBASE-5221) bin/hbase script doesn't look for Hadoop jars in the right place in trunk layout

[ https://issues.apache.org/jira/browse/HBASE-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13203801#comment-13203801 ] stack commented on HBASE-5221: -- @Roman Thanks for catching this. bin/hbase

[jira] [Commented] (HBASE-4762) ROOT and META region never be assigned if IOE throws in verifyRootRegionLocation

[ https://issues.apache.org/jira/browse/HBASE-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13203811#comment-13203811 ] stack commented on HBASE-4762: -- This should be less likely in TRUNK, right RAM?, since we

[jira] [Commented] (HBASE-5353) HA/Distributed HMaster via RegionServers

[ https://issues.apache.org/jira/browse/HBASE-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13203872#comment-13203872 ] stack commented on HBASE-5353: -- I'd say just run the master in-process w/ the regionserver.

[jira] [Commented] (HBASE-5270) Handle potential data loss due to concurrent processing of processFaileOver and ServerShutdownHandler

[ https://issues.apache.org/jira/browse/HBASE-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13203921#comment-13203921 ] stack commented on HBASE-5270: -- I was taking a look through HBASE-5179 and HBASE-4748 again,

[jira] [Commented] (HBASE-5270) Handle potential data loss due to concurrent processing of processFaileOver and ServerShutdownHandler

[ https://issues.apache.org/jira/browse/HBASE-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13203923#comment-13203923 ] stack commented on HBASE-5270: -- HBASE-3171 is the issue to purge root.

[jira] [Commented] (HBASE-5353) HA/Distributed HMaster via RegionServers

[ https://issues.apache.org/jira/browse/HBASE-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13204113#comment-13204113 ] stack commented on HBASE-5353: -- bq. Except it opens a new can of worms: where do you find the

[jira] [Commented] (HBASE-5353) HA/Distributed HMaster via RegionServers

[ https://issues.apache.org/jira/browse/HBASE-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13204268#comment-13204268 ] stack commented on HBASE-5353: -- bq. ...you only need to look two places if you have an issue.

[jira] [Commented] (HBASE-5355) Compressed RPC's for HBase

[ https://issues.apache.org/jira/browse/HBASE-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13204280#comment-13204280 ] stack commented on HBASE-5355: -- Could we do same prefix compression on the wire? Todd in

[jira] [Commented] (HBASE-5327) Print a message when an invalid hbase.rootdir is passed

[ https://issues.apache.org/jira/browse/HBASE-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13204287#comment-13204287 ] stack commented on HBASE-5327: -- The difference is that we get a nicer message on master crash

[jira] [Commented] (HBASE-3171) Drop ROOT and instead store META location(s) directly in ZooKeeper

[ https://issues.apache.org/jira/browse/HBASE-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13204307#comment-13204307 ] stack commented on HBASE-3171: -- I took a look at what is involved here. I first started out

[jira] [Commented] (HBASE-5363) Add rat check to run automatically on mvn build.

[ https://issues.apache.org/jira/browse/HBASE-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13204671#comment-13204671 ] stack commented on HBASE-5363: -- We already have this. See our pom: {code} plugin

[jira] [Commented] (HBASE-5327) Print a message when an invalid hbase.rootdir is passed

[ https://issues.apache.org/jira/browse/HBASE-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13204722#comment-13204722 ] stack commented on HBASE-5327: -- +1 Print a message when an invalid

[jira] [Commented] (HBASE-5363) Add rat check to run automatically on mvn build.

[ https://issues.apache.org/jira/browse/HBASE-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13204723#comment-13204723 ] stack commented on HBASE-5363: -- The rat plugin is pretty crappy in my experience too. Its

[jira] [Commented] (HBASE-5365) [book] adding description of compaction file selection to refGuide in Arch/Regions/Store

[ https://issues.apache.org/jira/browse/HBASE-5365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13204744#comment-13204744 ] stack commented on HBASE-5365: -- This doc patch is excellent. I thought default flush size in

[jira] [Commented] (HBASE-2375) Make decision to split based on aggregate size of all StoreFiles and revisit related config params

[ https://issues.apache.org/jira/browse/HBASE-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13204779#comment-13204779 ] stack commented on HBASE-2375: -- Doing first bullet point only sounds good. Lets file issues

[jira] [Commented] (HBASE-5367) [book] small formatting changes to compaction description in Arch/Regions/Store

[ https://issues.apache.org/jira/browse/HBASE-5367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13204782#comment-13204782 ] stack commented on HBASE-5367: -- In trunk this is 128M: {code}

[jira] [Commented] (HBASE-5367) [book] small formatting changes to compaction description in Arch/Regions/Store

[ https://issues.apache.org/jira/browse/HBASE-5367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13204800#comment-13204800 ] stack commented on HBASE-5367: -- {code} long flushSize =

<    3   4   5   6   7   8   9   10   11   12   >