[jira] [Updated] (HBASE-6160) META entries from daughters can be deleted before parent entries

[ https://issues.apache.org/jira/browse/HBASE-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6160: - Attachment: HBASE-6160_v2.patch What I applied to trunk (has Ted's suggested fixes) META

[jira] [Updated] (HBASE-6160) META entries from daughters can be deleted before parent entries

[ https://issues.apache.org/jira/browse/HBASE-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6160: - Attachment: HBASE-6160v2092.txt Here is patch I applied to 0.92 and 0.94 branches. META

[jira] [Updated] (HBASE-6160) META entries from daughters can be deleted before parent entries

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

[jira] [Updated] (HBASE-5609) Add the ability to pass additional information for slow query logging

[ https://issues.apache.org/jira/browse/HBASE-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-5609: - Fix Version/s: (was: 0.96.0) 0.94.1 Applied to 0.94 too at Lars' request.

[jira] [Updated] (HBASE-5609) Add the ability to pass additional information for slow query logging

[ https://issues.apache.org/jira/browse/HBASE-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-5609: - Attachment: HBASE-5609-v4-094.txt What I applied to 0.94. Add the ability to pass additional

[jira] [Commented] (HBASE-6160) META entries from daughters can be deleted before parent entries

[ https://issues.apache.org/jira/browse/HBASE-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13289615#comment-13289615 ] stack commented on HBASE-6160: -- bq. In some cases that we saw the region kept on growing.

[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=13289623#comment-13289623 ] stack commented on HBASE-6060: -- Why move this out of getRegionPlan? Don't we want

[jira] [Commented] (HBASE-6040) Use block encoding and HBase handled checksum verification in bulk loading using HFileOutputFormat

[ https://issues.apache.org/jira/browse/HBASE-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13289625#comment-13289625 ] stack commented on HBASE-6040: -- Make a new one at this stage I'd suggest Anoop; this one has

[jira] [Updated] (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:all-tabpanel ] stack updated HBASE-3537: - Attachment: disqus.txt This seems to work (disqus that is). Let me push it out. If anyone wants to be a

[jira] [Resolved] (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:all-tabpanel ] stack resolved HBASE-3537. -- Resolution: Fixed Fix Version/s: 0.96.0 Assignee: stack Ok. Deployed. Lets see how this

[jira] [Commented] (HBASE-6162) Move KeyValue to hbase-common module

[ https://issues.apache.org/jira/browse/HBASE-6162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13289729#comment-13289729 ] stack commented on HBASE-6162: -- That would make some sense Lars. Move

[jira] [Created] (HBASE-6167) Fix xinclude for docs broke when we multi-moduled

stack created HBASE-6167: Summary: Fix xinclude for docs broke when we multi-moduled Key: HBASE-6167 URL: https://issues.apache.org/jira/browse/HBASE-6167 Project: HBase Issue Type: Bug

[jira] [Resolved] (HBASE-6167) Fix xinclude for docs broke when we multi-moduled

[ https://issues.apache.org/jira/browse/HBASE-6167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-6167. -- Resolution: Fixed Fix Version/s: 0.96.0 Assignee: stack Committed to trunk.

[jira] [Updated] (HBASE-6167) Fix xinclude for docs broke when we multi-moduled

[ https://issues.apache.org/jira/browse/HBASE-6167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6167: - Attachment: xinclude.txt Small fix. Fix xinclude for docs broke when we multi-moduled

[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=13289853#comment-13289853 ] stack commented on HBASE-3537: -- I got the fb comment box up. It has the 'post to fb'

[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=13289936#comment-13289936 ] stack commented on HBASE-6060: -- @Chunhui That is inventive. It has merit in that we only do

[jira] [Commented] (HBASE-6053) Enhance TestRegionRebalancing test to be a system test

[ https://issues.apache.org/jira/browse/HBASE-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13289941#comment-13289941 ] stack commented on HBASE-6053: -- bq. But one could provide alternate implementations of the

[jira] [Commented] (HBASE-6135) Style the Web UI to use Twitter's Bootstrap.

[ https://issues.apache.org/jira/browse/HBASE-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13289946#comment-13289946 ] stack commented on HBASE-6135: -- Fancypants! Style the Web UI to use

[jira] [Commented] (HBASE-6168) [replication] Add replication zookeeper state documentation to replication.html

[ https://issues.apache.org/jira/browse/HBASE-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13289949#comment-13289949 ] stack commented on HBASE-6168: -- Excellent. Stuff like this is really great ...Side note: If

[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=13289971#comment-13289971 ] stack commented on HBASE-6060: -- @Ram I looked at Chunhui's suggestion and read it as a fix in

[jira] [Commented] (HBASE-6038) Add getClusterStatus PB-based call to HMasterInterface

[ https://issues.apache.org/jira/browse/HBASE-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13289975#comment-13289975 ] stack commented on HBASE-6038: -- Patch looks good Gregory. Is there some of hbase-6000 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=13289979#comment-13289979 ] stack commented on HBASE-6060: -- On znode check, yes, the rs is doing the checks before it

[jira] [Updated] (HBASE-6038) Add getClusterStatus PB-based call to HMasterInterface

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

[jira] [Created] (HBASE-6174) TestPBOnWritableRpc failing with -Dhadoop.profile=2.0

stack created HBASE-6174: Summary: TestPBOnWritableRpc failing with -Dhadoop.profile=2.0 Key: HBASE-6174 URL: https://issues.apache.org/jira/browse/HBASE-6174 Project: HBase Issue Type: Bug

[jira] [Resolved] (HBASE-6174) TestPBOnWritableRpc failing with -Dhadoop.profile=2.0

[ https://issues.apache.org/jira/browse/HBASE-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-6174. -- Resolution: Invalid Hmm... now it passes for me too. Sorry for the distraction. Resolving invalid.

[jira] [Created] (HBASE-6176) Take down the stargate reset doc or add pointer to manual documentation

stack created HBASE-6176: Summary: Take down the stargate reset doc or add pointer to manual documentation Key: HBASE-6176 URL: https://issues.apache.org/jira/browse/HBASE-6176 Project: HBase Issue

[jira] [Commented] (HBASE-5924) In the client code, don't wait for all the requests to be executed before resubmitting a request in error.

[ https://issues.apache.org/jira/browse/HBASE-5924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13290443#comment-13290443 ] stack commented on HBASE-5924: -- @nkeywal Did you add the history in the first place? Why is

[jira] [Commented] (HBASE-6176) Take down the stargate reset doc or add pointer to manual documentation

[ https://issues.apache.org/jira/browse/HBASE-6176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13290453#comment-13290453 ] stack commented on HBASE-6176: -- What is your wikiname (its been locked down because it was a

[jira] [Created] (HBASE-6179) Fix stylesheet broke since multimodule and address feedback gotten in new comment system

stack created HBASE-6179: Summary: Fix stylesheet broke since multimodule and address feedback gotten in new comment system Key: HBASE-6179 URL: https://issues.apache.org/jira/browse/HBASE-6179 Project:

[jira] [Updated] (HBASE-6179) Fix stylesheet broke since multimodule and address feedback gotten in new comment system

[ https://issues.apache.org/jira/browse/HBASE-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6179: - Attachment: 6179.txt Patch applied to trunk... reference stylesheet properly for multimodule context and fix

[jira] [Resolved] (HBASE-6179) Fix stylesheet broke since multimodule and address feedback gotten in new comment system

[ https://issues.apache.org/jira/browse/HBASE-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-6179. -- Resolution: Fixed Fix Version/s: 0.96.0 Assignee: stack Applied to trunk.

[jira] [Updated] (HBASE-6177) Add .idea to RAT excludes

[ https://issues.apache.org/jira/browse/HBASE-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6177: - Resolution: Fixed Fix Version/s: 0.96.0 Assignee: Elliott Clark Hadoop Flags: Reviewed

[jira] [Commented] (HBASE-6135) Style the Web UI to use Twitter's Bootstrap.

[ https://issues.apache.org/jira/browse/HBASE-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13290490#comment-13290490 ] stack commented on HBASE-6135: -- The metrics should go on a page of their own? Or, I suppose

[jira] [Commented] (HBASE-6135) Style the Web UI to use Twitter's Bootstrap.

[ https://issues.apache.org/jira/browse/HBASE-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13290497#comment-13290497 ] stack commented on HBASE-6135: -- I took a look see... its nicer than what we have. Have we

[jira] [Commented] (HBASE-6135) Style the Web UI to use Twitter's Bootstrap.

[ https://issues.apache.org/jira/browse/HBASE-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13290499#comment-13290499 ] stack commented on HBASE-6135: -- oh, how about a logo? Style the Web UI to

[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=13290510#comment-13290510 ] stack commented on HBASE-6175: -- This is the question you asked on the list Nicolas (why

[jira] [Commented] (HBASE-6162) Move KeyValue to hbase-common module

[ https://issues.apache.org/jira/browse/HBASE-6162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13290531#comment-13290531 ] stack commented on HBASE-6162: -- Ok. Lets leave comparators as they are for now. Can break

[jira] [Commented] (HBASE-6162) Move KeyValue to hbase-common module

[ https://issues.apache.org/jira/browse/HBASE-6162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13290556#comment-13290556 ] stack commented on HBASE-6162: -- When hbase-server compiles its tests, it does not include

[jira] [Commented] (HBASE-6176) Take down the stargate reset doc or add pointer to manual documentation

[ https://issues.apache.org/jira/browse/HBASE-6176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13290559#comment-13290559 ] stack commented on HBASE-6176: -- Try now Andrew. Take down the stargate

[jira] [Resolved] (HBASE-6168) [replication] Add replication zookeeper state documentation to replication.html

[ https://issues.apache.org/jira/browse/HBASE-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-6168. -- Resolution: Fixed Hadoop Flags: Reviewed Applied to trunk. Thanks for the patch Chris.

[jira] [Updated] (HBASE-6181) TestStoreFile fails with jdk1.7

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

[jira] [Commented] (HBASE-6183) hbase-common doesn't compile with jdk1.7

[ https://issues.apache.org/jira/browse/HBASE-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13290800#comment-13290800 ] stack commented on HBASE-6183: -- This is interesting Jimmy. I took a quick look around and

[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=13290805#comment-13290805 ] stack commented on HBASE-6060: -- Yes. Been trying to get to it all day but looks like it'll

[jira] [Commented] (HBASE-6162) Move KeyValue to hbase-common module

[ https://issues.apache.org/jira/browse/HBASE-6162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13290821#comment-13290821 ] stack commented on HBASE-6162: -- Yeah, lets undo these dependencies. TestConst we agreed

[jira] [Commented] (HBASE-6162) Move KeyValue to hbase-common module

[ https://issues.apache.org/jira/browse/HBASE-6162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13291053#comment-13291053 ] stack commented on HBASE-6162: -- @Matt Makes sense. I'd have seen that if I looked closer.

[jira] [Commented] (HBASE-5924) In the client code, don't wait for all the requests to be executed before resubmitting a request in error.

[ https://issues.apache.org/jira/browse/HBASE-5924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13291069#comment-13291069 ] stack commented on HBASE-5924: -- Upload v10 nkeywal and we'll commit it. Thanks for responses

[jira] [Commented] (HBASE-6183) hbase-common doesn't compile with jdk1.7

[ https://issues.apache.org/jira/browse/HBASE-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13291283#comment-13291283 ] stack commented on HBASE-6183: -- Can you just do -DcompileSource=1.7 when you invoke mvn?

[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=13291416#comment-13291416 ] stack commented on HBASE-6060: -- I think I understand this patch now. In AM, we introduce a

[jira] [Commented] (HBASE-5726) TestSplitTransactionOnCluster occasionally failing

[ https://issues.apache.org/jira/browse/HBASE-5726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13291418#comment-13291418 ] stack commented on HBASE-5726: -- +1 Lets try it Ted.

[jira] [Commented] (HBASE-6173) hbck check specified tables only

[ https://issues.apache.org/jira/browse/HBASE-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13291420#comment-13291420 ] stack commented on HBASE-6173: -- @Jimmy You have a +1 from Jon. Go commit?

[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=13291426#comment-13291426 ] stack commented on HBASE-6060: -- My other high level comment is: 3. This patch will not fix a

[jira] [Commented] (HBASE-6191) There should be a serach option in the book which helps you to search the content in the book.

[ https://issues.apache.org/jira/browse/HBASE-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13291551#comment-13291551 ] stack commented on HBASE-6191: -- @Otis Can you help here? Can we have a book checkbox in

[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: - Attachment: 6060_suggestion_based_off_v3.patch Suggestion. Regions's in OPENING state from

[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=13291568#comment-13291568 ] stack commented on HBASE-6060: -- @Enis Yeah, its a big problem. Ram and Rajeshbabu, I just

[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=13291575#comment-13291575 ] stack commented on HBASE-6060: -- bq. We are only maintaining regions and the RITS. not the

[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: - Attachment: 6060_suggestion2_based_off_v3.patch v2 is more basic still. It undoes the

[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=13291835#comment-13291835 ] stack commented on HBASE-6060: -- bq. Excluding this server we will call one more assign

[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=13292114#comment-13292114 ] stack commented on HBASE-6060: -- Just some notes after looking more at this stuff. We have

[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: - Attachment: 6060_alternative_suggestion.txt What about this Ram? Its about four lines. I haven't tried it yet.

[jira] [Commented] (HBASE-6194) add open time for a region and list recently closed regions in a regionserver UI

[ https://issues.apache.org/jira/browse/HBASE-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292429#comment-13292429 ] stack commented on HBASE-6194: -- +1 good idea. Could even do it w/ color scheme regions

[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=13292470#comment-13292470 ] stack commented on HBASE-6060: -- bq. We need to consider regions in OPEN state also(along with

[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=13292475#comment-13292475 ] stack commented on HBASE-6060: -- bq. But the gain with bulk assignment is its faster which we

[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=13292476#comment-13292476 ] stack commented on HBASE-6060: -- @rajeshbabu So, you are allowing the single-assign to

[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=13292589#comment-13292589 ] stack commented on HBASE-6060: -- Rajesh says: bq. Lets suppose Region server went down after

[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=13292835#comment-13292835 ] stack commented on HBASE-6060: -- What do I have to change in that section of code? It seems

[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=13292884#comment-13292884 ] stack commented on HBASE-6060: -- bq. Or else if the region has been moved to OPENING and the

[jira] [Created] (HBASE-6198) Sometimes we synchronize on RegionState instance updating it, most of the time we don't. Fix

stack created HBASE-6198: Summary: Sometimes we synchronize on RegionState instance updating it, most of the time we don't. Fix Key: HBASE-6198 URL: https://issues.apache.org/jira/browse/HBASE-6198 Project:

[jira] [Created] (HBASE-6199) Change PENDING_OPEN scope from pre-rpc open to OPENING to just post-rpc open to OPENING

stack created HBASE-6199: Summary: Change PENDING_OPEN scope from pre-rpc open to OPENING to just post-rpc open to OPENING Key: HBASE-6199 URL: https://issues.apache.org/jira/browse/HBASE-6199 Project: HBase

[jira] [Updated] (HBASE-6199) Change PENDING_OPEN scope from pre-rpc open to OPENING to just post-rpc open to OPENING

[ https://issues.apache.org/jira/browse/HBASE-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6199: - Attachment: pending_open.txt Lets see how this patch does. Change PENDING_OPEN scope from

[jira] [Updated] (HBASE-6199) Change PENDING_OPEN scope from pre-rpc open to OPENING to just post-rpc open to OPENING

[ https://issues.apache.org/jira/browse/HBASE-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6199: - Attachment: pending_open2.txt First patch had mistake in it. Change PENDING_OPEN scope from

[jira] [Updated] (HBASE-6199) Change PENDING_OPEN scope from pre-rpc open to OPENING to just post-rpc open to OPENING

[ https://issues.apache.org/jira/browse/HBASE-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6199: - Assignee: stack Status: Patch Available (was: Open) Change PENDING_OPEN scope from pre-rpc open to

[jira] [Updated] (HBASE-6199) Change PENDING_OPEN scope from pre-rpc open to OPENING to just post-rpc open to OPENING

[ https://issues.apache.org/jira/browse/HBASE-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6199: - Attachment: pending_open3.txt Fix comments. Change PENDING_OPEN scope from pre-rpc open to

[jira] [Updated] (HBASE-6199) Change PENDING_OPEN scope from pre-rpc open to OPENING to just post-rpc open to OPENING

[ https://issues.apache.org/jira/browse/HBASE-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6199: - Status: Open (was: Patch Available) Change PENDING_OPEN scope from pre-rpc open to OPENING to just

[jira] [Updated] (HBASE-6199) Change PENDING_OPEN scope from pre-rpc open to OPENING to just post-rpc open to OPENING

[ https://issues.apache.org/jira/browse/HBASE-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6199: - Status: Patch Available (was: Open) Change PENDING_OPEN scope from pre-rpc open to OPENING to just

[jira] [Updated] (HBASE-6199) Change PENDING_OPEN scope from pre-rpc open to OPENING to just post-rpc open to OPENING

[ https://issues.apache.org/jira/browse/HBASE-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6199: - Attachment: 6199v4.txt Cleaner version (the v3 didn't apply to fresh trunk) Change

[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=13293390#comment-13293390 ] stack commented on HBASE-6060: -- bq. Now after calling openregion if the OpenRegionHandler is

[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=13293706#comment-13293706 ] stack commented on HBASE-6060: -- @Ram So, the rpc returns successfully. The very next step is

[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=13293973#comment-13293973 ] stack commented on HBASE-6060: -- @Ram Thinking on it, the way to plug the hole you and Rajesh

[jira] [Commented] (HBASE-6185) Update javadoc for ConstantSizeRegionSplitPolicy class

[ https://issues.apache.org/jira/browse/HBASE-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294150#comment-13294150 ] stack commented on HBASE-6185: -- @nneverwei Thanks for doing this. Should the patch also

[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=13295198#comment-13295198 ] stack commented on HBASE-6205: -- @Chunhui Why a special hbase trash dir? Why not just use the

[jira] [Commented] (HBASE-5924) In the client code, don't wait for all the requests to be executed before resubmitting a request in error.

[ https://issues.apache.org/jira/browse/HBASE-5924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13295204#comment-13295204 ] stack commented on HBASE-5924: -- I took a look at committed patch. This looks great.

[jira] [Commented] (HBASE-6195) Increment data will be lost when the memstore is flushed

[ https://issues.apache.org/jira/browse/HBASE-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13295241#comment-13295241 ] stack commented on HBASE-6195: -- Xing Nice work. When you run MultiThreadsIncrement w/ your

[jira] [Updated] (HBASE-6162) Move KeyValue to hbase-common module

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

[jira] [Commented] (HBASE-6192) Document ACL matrix in the book

[ https://issues.apache.org/jira/browse/HBASE-6192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13295259#comment-13295259 ] stack commented on HBASE-6192: -- @Laxman I'll take care of convertion to our doc format. Just

[jira] [Commented] (HBASE-3909) Add dynamic config

[ https://issues.apache.org/jira/browse/HBASE-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13295267#comment-13295267 ] stack commented on HBASE-3909: -- bq. My understanding is that all configuration properties

[jira] [Commented] (HBASE-5998) Bulk assignment: regionserver optimization by using a temporary cache for table descriptors when receveing an open regions request

[ https://issues.apache.org/jira/browse/HBASE-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13295271#comment-13295271 ] stack commented on HBASE-5998: -- I took a look at backporting at Anoop's request. Its not a

[jira] [Commented] (HBASE-6202) Medium tests fail with jdk1.7

[ https://issues.apache.org/jira/browse/HBASE-6202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13295272#comment-13295272 ] stack commented on HBASE-6202: -- Changes seem reasonable Jimmy. Why you think they are needed

[jira] [Commented] (HBASE-4391) Add ability to start RS as root and call mlockall

[ https://issues.apache.org/jira/browse/HBASE-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13295276#comment-13295276 ] stack commented on HBASE-4391: -- @Matteo What about Andrew's suggested location for the src

[jira] [Updated] (HBASE-6197) HRegion's append operation may lose data

[ https://issues.apache.org/jira/browse/HBASE-6197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6197: - Resolution: Fixed Fix Version/s: 0.96.0 Status: Resolved (was: Patch Available) Ted committed

[jira] [Created] (HBASE-6210) Backport HBASE-6197 to 0.94 and 0.92?

stack created HBASE-6210: Summary: Backport HBASE-6197 to 0.94 and 0.92? Key: HBASE-6210 URL: https://issues.apache.org/jira/browse/HBASE-6210 Project: HBase Issue Type: Bug Reporter:

[jira] [Commented] (HBASE-6197) HRegion's append operation may lose data

[ https://issues.apache.org/jira/browse/HBASE-6197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13295297#comment-13295297 ] stack commented on HBASE-6197: -- I made HBASE-6210 for backport. HRegion's

[jira] [Updated] (HBASE-6185) Update javadoc for ConstantSizeRegionSplitPolicy class

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

[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=13295311#comment-13295311 ] stack commented on HBASE-6060: -- bq. But i agree two systems AM and SSH take decision based on

[jira] [Commented] (HBASE-6135) Style the Web UI to use Twitter's Bootstrap.

[ https://issues.apache.org/jira/browse/HBASE-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13295323#comment-13295323 ] stack commented on HBASE-6135: -- Ok if I commit this? Can fine tune in other issues?

[jira] [Updated] (HBASE-6135) Style the Web UI to use Twitter's Bootstrap.

[ https://issues.apache.org/jira/browse/HBASE-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6135: - Attachment: HBASE-6135-2.patch Elliott's patch only w/ the logo in src/resources dir so can be found when run

[jira] [Updated] (HBASE-6135) Style the Web UI to use Twitter's Bootstrap.

[ https://issues.apache.org/jira/browse/HBASE-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6135: - Attachment: HBASE-6135-5.patch What I committed. Style the Web UI to use Twitter's Bootstrap.

[jira] [Resolved] (HBASE-6135) Style the Web UI to use Twitter's Bootstrap.

[ https://issues.apache.org/jira/browse/HBASE-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-6135. -- Resolution: Fixed Hadoop Flags: Reviewed Thanks for the patch Elliott. Nice. Style

[jira] [Commented] (HBASE-5564) Bulkload is discarding duplicate records

[ https://issues.apache.org/jira/browse/HBASE-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13295345#comment-13295345 ] stack commented on HBASE-5564: -- +1 on commit. Bulkload is discarding

[jira] [Commented] (HBASE-6196) MR testcases does not run with hadoop - 2.0.

[ https://issues.apache.org/jira/browse/HBASE-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13295348#comment-13295348 ] stack commented on HBASE-6196: -- Want to update the JIRA subject then Ram to reflect the new

[jira] [Commented] (HBASE-6201) HBase integration/system tests

[ https://issues.apache.org/jira/browse/HBASE-6201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13295354#comment-13295354 ] stack commented on HBASE-6201: -- Thanks for doing this Enis. +1 on making subjiras off this

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