[jira] [Resolved] (HBASE-3065) Retry all 'retryable' zk operations; e.g. connection loss

[ https://issues.apache.org/jira/browse/HBASE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-3065. -- Resolution: Fixed Committed to TRUNK Liyin. This may have broken distributed split test. Will look into that

[jira] [Updated] (HBASE-4092) performance.xml - adding batch-loading entry for using deferred log flush

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

[jira] [Updated] (HBASE-4091) book.xml - description of block cache in arch, description of inMemory in schema creation

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

[jira] [Updated] (HBASE-4090) book.xml - minor clarification of block cache metric

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

[jira] [Updated] (HBASE-3065) Retry all 'retryable' zk operations; e.g. connection loss

[ https://issues.apache.org/jira/browse/HBASE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-3065: - Attachment: 3065-v4.txt Update to trunk, fix failing TestHMasterRPC and some cleanup on Liyin's v3 patch. > Ret

[jira] [Updated] (HBASE-4138) If zookeeper.znode.parent is not specifed explicitly in Client code then HTable object loops continuously waiting for the root region by using /hbase as the base node.

[ https://issues.apache.org/jira/browse/HBASE-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-4138: -- Fix Version/s: (was: 0.90.4) 0.92.0 Status: Pa

[jira] [Commented] (HBASE-3900) Expose progress of a major compaction in UI and/or in shell

[ https://issues.apache.org/jira/browse/HBASE-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072197#comment-13072197 ] stack commented on HBASE-3900: -- I added comments over on github repeated here: @brad Patch l

[jira] [Updated] (HBASE-4138) If zookeeper.znode.parent is not specifed explicitly in Client code then HTable object loops continuously waiting for the root region by using /hbase as the base node.

[ https://issues.apache.org/jira/browse/HBASE-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-4138: -- Attachment: HBASE-4138_trunk_1.patch > If zookeeper.znode.parent is not specife

[jira] [Commented] (HBASE-3845) data loss because lastSeqWritten can miss memstore edits

[ https://issues.apache.org/jira/browse/HBASE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072189#comment-13072189 ] Prakash Khemani commented on HBASE-3845: I agree that the test case is OK. We shou

[jira] [Commented] (HBASE-3845) data loss because lastSeqWritten can miss memstore edits

[ https://issues.apache.org/jira/browse/HBASE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072186#comment-13072186 ] ramkrishna.s.vasudevan commented on HBASE-3845: --- The testcase TestResettingC

[jira] [Commented] (HBASE-4032) HBASE-451 improperly breaks public API HRegionInfo#getTableDesc

[ https://issues.apache.org/jira/browse/HBASE-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072179#comment-13072179 ] stack commented on HBASE-4032: -- I could note that in the deprecated note AND leave this expen

[jira] [Commented] (HBASE-4032) HBASE-451 improperly breaks public API HRegionInfo#getTableDesc

[ https://issues.apache.org/jira/browse/HBASE-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072174#comment-13072174 ] Ted Yu commented on HBASE-4032: --- HRegionInfo#getTableNameAsString() can be used in place of

[jira] [Commented] (HBASE-4032) HBASE-451 improperly breaks public API HRegionInfo#getTableDesc

[ https://issues.apache.org/jira/browse/HBASE-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072172#comment-13072172 ] stack commented on HBASE-4032: -- Whats the equivalent Ted? > HBASE-451 improperly breaks publ

[jira] [Commented] (HBASE-4032) HBASE-451 improperly breaks public API HRegionInfo#getTableDesc

[ https://issues.apache.org/jira/browse/HBASE-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072168#comment-13072168 ] Ted Yu commented on HBASE-4032: --- The most common usage of HRegionInfo#getTableDesc is hri.g

[jira] [Commented] (HBASE-4015) Refactor the TimeoutMonitor to make it less racy

[ https://issues.apache.org/jira/browse/HBASE-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072166#comment-13072166 ] stack commented on HBASE-4015: -- No. Too important. > Refactor the TimeoutMonitor to make it

[jira] [Commented] (HBASE-4015) Refactor the TimeoutMonitor to make it less racy

[ https://issues.apache.org/jira/browse/HBASE-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072162#comment-13072162 ] Ted Yu commented on HBASE-4015: --- Shall we punt this to 0.94 ? > Refactor the TimeoutMonitor

[jira] [Resolved] (HBASE-3447) Split parents ending up deployed along with daughters

[ https://issues.apache.org/jira/browse/HBASE-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-3447. -- Resolution: Fixed Resolving. Reopen if think otherwise. > Split parents ending up deployed along with daughte

[jira] [Commented] (HBASE-3447) Split parents ending up deployed along with daughters

[ https://issues.apache.org/jira/browse/HBASE-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072160#comment-13072160 ] Ted Yu commented on HBASE-3447: --- HBASE-3446 is a blocker which will be fixed for 0.92 I thi

[jira] [Updated] (HBASE-4143) HTable.doPut(List) should check the writebuffer length every so often

[ https://issues.apache.org/jira/browse/HBASE-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-4143: -- Resolution: Fixed Hadoop Flags: [Reviewed] Status: Resolved (was: Patch Available) > HTable.do

[jira] [Commented] (HBASE-4143) HTable.doPut(List) should check the writebuffer length every so often

[ https://issues.apache.org/jira/browse/HBASE-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072119#comment-13072119 ] Ted Yu commented on HBASE-4143: --- Integrated to branch and TRUNK. Thanks for the patch Doug.

[jira] [Updated] (HBASE-4143) HTable.doPut(List) should check the writebuffer length every so often

[ https://issues.apache.org/jira/browse/HBASE-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-4143: -- Summary: HTable.doPut(List) should check the writebuffer length every so often (was: HTable.doPut(List) should

[jira] [Commented] (HBASE-3447) Split parents ending up deployed along with daughters

[ https://issues.apache.org/jira/browse/HBASE-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072092#comment-13072092 ] stack commented on HBASE-3447: -- I think we should close this issue. Todd suggests: bq. But

[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072091#comment-13072091 ] Andrew Purtell commented on HBASE-1938: --- I see the same type of results with either

[jira] [Resolved] (HBASE-4042) TestDistributedLogSplitting broke on trunk

[ https://issues.apache.org/jira/browse/HBASE-4042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-4042. -- Resolution: Invalid This test seems to pass now (Though it looks like still problems to address w/ how test is

[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072085#comment-13072085 ] nkeywal commented on HBASE-1938: Thank you. It's interesting because the tests with 15

[jira] [Commented] (HBASE-3845) data loss because lastSeqWritten can miss memstore edits

[ https://issues.apache.org/jira/browse/HBASE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072082#comment-13072082 ] Vlad Dogaru commented on HBASE-3845: This patch seems to break TestResettingCounters f

[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072073#comment-13072073 ] Andrew Purtell commented on HBASE-1938: --- This is a representative test with 0.90 bra

[jira] [Commented] (HBASE-4143) HTable.doPut(List) should check the writebuffer lengh every so often

[ https://issues.apache.org/jira/browse/HBASE-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072065#comment-13072065 ] Doug Meil commented on HBASE-4143: -- Andy, I'm glad you made that doc-change because it ex

[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072064#comment-13072064 ] nkeywal commented on HBASE-1938: Yes, I can provide a patch with all the changes except th

[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072061#comment-13072061 ] stack commented on HBASE-1938: -- Reverted 20110726_1938_MemStore.patch for now on TRUNK (left

[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072058#comment-13072058 ] stack commented on HBASE-1938: -- Let me back out application of MemStore patch till we figure

[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072057#comment-13072057 ] Andrew Purtell commented on HBASE-1938: --- I ran 3 consecutive tests with MemStore cha

[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072052#comment-13072052 ] nkeywal commented on HBASE-1938: Ok, that's strange. This patch includes multiple small mo

[jira] [Updated] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-1938: -- Fix Version/s: 0.90.4 > Make in-memory table scanning faster >

[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072051#comment-13072051 ] Andrew Purtell commented on HBASE-1938: --- Applied 20110726_1938_KeyValueSkipListSet a

[jira] [Commented] (HBASE-4143) HTable.doPut(List) should check the writebuffer lengh every so often

[ https://issues.apache.org/jira/browse/HBASE-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072048#comment-13072048 ] Andrew Purtell commented on HBASE-4143: --- +1 on second patch. I made just a document

[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072046#comment-13072046 ] Andrew Purtell commented on HBASE-1938: --- bq. the bits that change the read-point see

[jira] [Commented] (HBASE-3857) Change the HFile Format

[ https://issues.apache.org/jira/browse/HBASE-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072033#comment-13072033 ] Mikhail Bautin commented on HBASE-3857: --- @Todd: thank you for your comments! @Michae

[jira] [Commented] (HBASE-3857) Change the HFile Format

[ https://issues.apache.org/jira/browse/HBASE-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072027#comment-13072027 ] stack commented on HBASE-3857: -- @Mikhail You see Todd's comments. Will you have a chance to

[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072025#comment-13072025 ] Todd Lipcon commented on HBASE-1938: The iterator one seems like a no-brainer for bran

[jira] [Commented] (HBASE-4143) HTable.doPut(List) should check the writebuffer lengh every so often

[ https://issues.apache.org/jira/browse/HBASE-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072008#comment-13072008 ] Ted Yu commented on HBASE-4143: --- +1 on second patch. > HTable.doPut(List) should check the

[jira] [Commented] (HBASE-4143) HTable.doPut(List) should check the writebuffer lengh every so often

[ https://issues.apache.org/jira/browse/HBASE-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072003#comment-13072003 ] Doug Meil commented on HBASE-4143: -- I had this vision of people at some point wanting thi

[jira] [Updated] (HBASE-4143) HTable.doPut(List) should check the writebuffer lengh every so often

[ https://issues.apache.org/jira/browse/HBASE-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Meil updated HBASE-4143: - Attachment: (was: client_HBASE_4143.patch) > HTable.doPut(List) should check the writebuffer lengh ev

[jira] [Updated] (HBASE-4143) HTable.doPut(List) should check the writebuffer lengh every so often

[ https://issues.apache.org/jira/browse/HBASE-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Meil updated HBASE-4143: - Attachment: client_HBASE_4143.patch > HTable.doPut(List) should check the writebuffer lengh every so ofte

[jira] [Commented] (HBASE-4143) HTable.doPut(List) should check the writebuffer lengh every so often

[ https://issues.apache.org/jira/browse/HBASE-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071994#comment-13071994 ] Ted Yu commented on HBASE-4143: --- {code} + private int doPutWbCheck = 10;// i.e., doPut

[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071991#comment-13071991 ] Andrew Purtell commented on HBASE-1938: --- 20110726_1938* apply cleanly to 0.90 as wel

[jira] [Updated] (HBASE-4143) HTable.doPut(List) should check the writebuffer lengh every so often

[ https://issues.apache.org/jira/browse/HBASE-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Meil updated HBASE-4143: - Status: Patch Available (was: Open) > HTable.doPut(List) should check the writebuffer lengh every so oft

[jira] [Commented] (HBASE-4143) HTable.doPut(List) should check the writebuffer lengh every so often

[ https://issues.apache.org/jira/browse/HBASE-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071982#comment-13071982 ] Doug Meil commented on HBASE-4143: -- Changed HTable.doPut for periodic check of in-loop wr

[jira] [Updated] (HBASE-4143) HTable.doPut(List) should check the writebuffer lengh every so often

[ https://issues.apache.org/jira/browse/HBASE-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Meil updated HBASE-4143: - Attachment: client_HBASE_4143.patch > HTable.doPut(List) should check the writebuffer lengh every so ofte

[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071973#comment-13071973 ] Hudson commented on HBASE-1938: --- Integrated in HBase-TRUNK #2056 (See [https://builds.apach

[jira] [Commented] (HBASE-4137) Implementation of Distributed Hash Table(DHT) for lookup service

[ https://issues.apache.org/jira/browse/HBASE-4137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071947#comment-13071947 ] stack commented on HBASE-4137: -- bq. Are they stored in two different special machines in whic

[jira] [Updated] (HBASE-4032) HBASE-451 improperly breaks public API HRegionInfo#getTableDesc

[ https://issues.apache.org/jira/browse/HBASE-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-4032: - Attachment: 4032.txt This is pretty horrid but might be enough? What you think Andrew? > HBASE-451 improperly b

[jira] [Commented] (HBASE-3918) When assigning regions to an address, check the regionserver is actually online first

[ https://issues.apache.org/jira/browse/HBASE-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071935#comment-13071935 ] stack commented on HBASE-3918: -- bq. How was this copying done? It was hdfs copy I believe (N

[jira] [Commented] (HBASE-4120) isolation and allocation

[ https://issues.apache.org/jira/browse/HBASE-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071891#comment-13071891 ] Todd Lipcon commented on HBASE-4120: FWIW, I've heard rumblings out of Google that the

[jira] [Updated] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-1938: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to TRUNK. Nice one nkeywal (I close

[jira] [Commented] (HBASE-4120) isolation and allocation

[ https://issues.apache.org/jira/browse/HBASE-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071882#comment-13071882 ] stack commented on HBASE-4120: -- @Jeff We have some notion already of 'priority' where .META.

[jira] [Commented] (HBASE-4113) Add createAsync and splits by start and end key to the shell

[ https://issues.apache.org/jira/browse/HBASE-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071879#comment-13071879 ] stack commented on HBASE-4113: -- +1 on commit, if it works (smile). Nice one. > Add createAs

[jira] [Commented] (HBASE-3899) enhance HBase RPC to support free-ing up server handler threads even if response is not ready

[ https://issues.apache.org/jira/browse/HBASE-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071878#comment-13071878 ] stack commented on HBASE-3899: -- @Vlad (& Jon) Sorry about the false alarm... Passes for me to

[jira] [Commented] (HBASE-3899) enhance HBase RPC to support free-ing up server handler threads even if response is not ready

[ https://issues.apache.org/jira/browse/HBASE-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071864#comment-13071864 ] Vlad Dogaru commented on HBASE-3899: Just ran the test a few times, it passed each tim

[jira] [Commented] (HBASE-3899) enhance HBase RPC to support free-ing up server handler threads even if response is not ready

[ https://issues.apache.org/jira/browse/HBASE-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071861#comment-13071861 ] Jonathan Gray commented on HBASE-3899: -- Test passes for me on trunk. > enhance HBase

[jira] [Commented] (HBASE-4113) Add createAsync and splits by start and end key to the shell

[ https://issues.apache.org/jira/browse/HBASE-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071851#comment-13071851 ] Ted Yu commented on HBASE-4113: --- +1 on patch version 2. > Add createAsync and splits by sta

[jira] [Commented] (HBASE-4003) Cleanup Calls Conservatively On Timeout

[ https://issues.apache.org/jira/browse/HBASE-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071845#comment-13071845 ] Karthick Sankarachary commented on HBASE-4003: -- Hi Stack, I think I just nee

[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071842#comment-13071842 ] nkeywal commented on HBASE-1938: bq. Any chance of our calling a 'next' without doing a '

[jira] [Commented] (HBASE-4120) isolation and allocation

[ https://issues.apache.org/jira/browse/HBASE-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071807#comment-13071807 ] Jeff Whiting commented on HBASE-4120: - I would really like to see the priorities in hb

[jira] [Created] (HBASE-4144) RS doesnot abort if the initialization of RS fails

RS doesnot abort if the initialization of RS fails --- Key: HBASE-4144 URL: https://issues.apache.org/jira/browse/HBASE-4144 Project: HBase Issue Type: Bug Components: regionserver

[jira] [Commented] (HBASE-3918) When assigning regions to an address, check the regionserver is actually online first

[ https://issues.apache.org/jira/browse/HBASE-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071781#comment-13071781 ] ramkrishna.s.vasudevan commented on HBASE-3918: --- @Stack. {noformat} This one

[jira] [Assigned] (HBASE-4143) HTable.doPut(List) should check the writebuffer lengh every so often

[ https://issues.apache.org/jira/browse/HBASE-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Meil reassigned HBASE-4143: Assignee: Doug Meil > HTable.doPut(List) should check the writebuffer lengh every so often > --

[jira] [Updated] (HBASE-4143) HTable.doPut(List) should check the writebuffer lengh every so often

[ https://issues.apache.org/jira/browse/HBASE-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Meil updated HBASE-4143: - Description: This came up on a dist-list conversation between Andy P., Ted Yu, and myself. Andy noted t

[jira] [Created] (HBASE-4143) HTable.doPut(List) should check the writebuffer lengh every so often

HTable.doPut(List) should check the writebuffer lengh every so often Key: HBASE-4143 URL: https://issues.apache.org/jira/browse/HBASE-4143 Project: HBase Issue Type: Improv

[jira] [Commented] (HBASE-4120) isolation and allocation

[ https://issues.apache.org/jira/browse/HBASE-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071650#comment-13071650 ] Liu Jia commented on HBASE-4120: We think the isolation and allocation tool is very compac

[jira] [Updated] (HBASE-4120) isolation and allocation

[ https://issues.apache.org/jira/browse/HBASE-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liu Jia updated HBASE-4120: --- Attachment: Design_document_for_HBase_isolation_and_allocation_Revised.pdf > isolation and allocation > -

[jira] [Commented] (HBASE-4137) Implementation of Distributed Hash Table(DHT) for lookup service

[ https://issues.apache.org/jira/browse/HBASE-4137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071638#comment-13071638 ] vamshi commented on HBASE-4137: --- Hi stack, i thought in some different manner and i posted t

[jira] [Commented] (HBASE-3432) [hbck] Add "remove table" switch

[ https://issues.apache.org/jira/browse/HBASE-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071625#comment-13071625 ] vamshi commented on HBASE-3432: --- Hi Lars, i have small doubt regarding Root and .META. Actua

[jira] [Updated] (HBASE-3067) in_memory column family records should be available in memory past memstore flush if total memory to hbase > memory to memstore

[ https://issues.apache.org/jira/browse/HBASE-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sayyid Amin updated HBASE-3067: --- Summary: in_memory column family records should be available in memory past memstore flush if total m

[jira] [Commented] (HBASE-4083) If Enable table is not completed and is partial, then scanning of the table is not working

[ https://issues.apache.org/jira/browse/HBASE-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071591#comment-13071591 ] Hudson commented on HBASE-4083: --- Integrated in HBase-TRUNK #2055 (See [https://builds.apach