[jira] [Updated] (HBASE-4105) Stargate does not support Content-Type: application/json and Content-Encoding: gzip in parallel

[ https://issues.apache.org/jira/browse/HBASE-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-4105: -- Attachment: HBASE-4105.patch Attached patch for this issue. Also fixes a problem reported on

[jira] [Updated] (HBASE-4105) Stargate does not support Content-Type: application/json and Content-Encoding: gzip in parallel

[ https://issues.apache.org/jira/browse/HBASE-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-4105: -- Status: Patch Available (was: Open) Stargate does not support Content-Type: application/json

[jira] [Updated] (HBASE-4105) Stargate does not support Content-Type: application/json and Content-Encoding: gzip in parallel

[ https://issues.apache.org/jira/browse/HBASE-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-4105: -- Fix Version/s: 0.90.4 Stargate does not support Content-Type: application/json and

[jira] [Commented] (HBASE-4105) Stargate does not support Content-Type: application/json and Content-Encoding: gzip in parallel

[ https://issues.apache.org/jira/browse/HBASE-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13069912#comment-13069912 ] stack commented on HBASE-4105: -- +1 Commit it I'd say. Ive tagged RC0. I think its going to

[jira] [Created] (HBASE-4130) HTable.flushCommits throws IndexOutOfBoundsException

HTable.flushCommits throws IndexOutOfBoundsException Key: HBASE-4130 URL: https://issues.apache.org/jira/browse/HBASE-4130 Project: HBase Issue Type: Bug Components: client

[jira] [Commented] (HBASE-4130) HTable.flushCommits throws IndexOutOfBoundsException

[ https://issues.apache.org/jira/browse/HBASE-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13069962#comment-13069962 ] Ted Yu commented on HBASE-4130: --- HTable has always been thread unsafe. HTable.flushCommits

[jira] [Commented] (HBASE-4128) Detect whether there was zookeeper ensemble hanging from previous build

[ https://issues.apache.org/jira/browse/HBASE-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13069976#comment-13069976 ] Eric Charles commented on HBASE-4128: - Should we also detect hanged master and region

[jira] [Updated] (HBASE-4128) Detect whether there was zookeeper ensemble, master or region server hanging from previous build

[ https://issues.apache.org/jira/browse/HBASE-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-4128: -- Description: Quite often, we see unit test(s) time out after 15 minutes. One example was TestShell:

[jira] [Updated] (HBASE-4105) Stargate does not support Content-Type: application/json and Content-Encoding: gzip in parallel

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

[jira] [Commented] (HBASE-4105) Stargate does not support Content-Type: application/json and Content-Encoding: gzip in parallel

[ https://issues.apache.org/jira/browse/HBASE-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070033#comment-13070033 ] Andrew Purtell commented on HBASE-4105: --- Added a test case for checking that the

[jira] [Updated] (HBASE-4116) [stargate] StringIndexOutOfBoundsException in row spec parse

[ https://issues.apache.org/jira/browse/HBASE-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-4116: -- Attachment: HBASE-4116.patch Converted Allan's description into a patch. [stargate]

[jira] [Resolved] (HBASE-4116) [stargate] StringIndexOutOfBoundsException in row spec parse

[ https://issues.apache.org/jira/browse/HBASE-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HBASE-4116. --- Resolution: Fixed Fix Version/s: 0.90.4 Assignee: (was: Andrew Purtell)

[jira] [Commented] (HBASE-4128) Detect whether there was zookeeper ensemble, master or region server hanging from previous build

[ https://issues.apache.org/jira/browse/HBASE-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070062#comment-13070062 ] stack commented on HBASE-4128: -- @Eric Yes. We'll now jps as first thing we do before build.

[jira] [Updated] (HBASE-4129) hbase-3872 added a warn message 'CatalogJanitor: Daughter regiondir does not exist' that is triggered though its often legit that daughter is not present

[ https://issues.apache.org/jira/browse/HBASE-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-4129: - Attachment: 3872.txt So, I think the issue is that the HRegionInfo comparator is sorting daughters' before

[jira] [Commented] (HBASE-4130) HTable.flushCommits throws IndexOutOfBoundsException

[ https://issues.apache.org/jira/browse/HBASE-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070065#comment-13070065 ] stack commented on HBASE-4130: -- Yes, what Ted says. At head of class it says This class 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-tabpanelfocusedCommentId=13070067#comment-13070067 ] stack commented on HBASE-1938: -- bq. I modified the unit test to make it work with the trunk

[jira] [Commented] (HBASE-4105) Stargate does not support Content-Type: application/json and Content-Encoding: gzip in parallel

[ https://issues.apache.org/jira/browse/HBASE-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070070#comment-13070070 ] Hudson commented on HBASE-4105: --- Integrated in HBase-TRUNK #2047 (See

[jira] [Created] (HBASE-4131) Make the Replication Service pluggable via a standard interface definition

Make the Replication Service pluggable via a standard interface definition -- Key: HBASE-4131 URL: https://issues.apache.org/jira/browse/HBASE-4131 Project: HBase Issue

[jira] [Commented] (HBASE-4116) [stargate] StringIndexOutOfBoundsException in row spec parse

[ https://issues.apache.org/jira/browse/HBASE-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070082#comment-13070082 ] Hudson commented on HBASE-4116: --- Integrated in HBase-TRUNK #2048 (See

[jira] [Commented] (HBASE-4131) Make the Replication Service pluggable via a standard interface definition

[ https://issues.apache.org/jira/browse/HBASE-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070083#comment-13070083 ] dhruba borthakur commented on HBASE-4131: - To keep compatibility with the

[jira] [Updated] (HBASE-4132) Extend the WALObserver API to accomodate log archival

[ https://issues.apache.org/jira/browse/HBASE-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HBASE-4132: Attachment: walArchive.txt Added two new methods to the WALObserver interface: {code}

[jira] [Updated] (HBASE-4132) Extend the WALObserver API to accomodate log archival

[ https://issues.apache.org/jira/browse/HBASE-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-4132: - Fix Version/s: 0.92.0 Release Note: Add pre and post archiving methods to WALObserver Status:

[jira] [Commented] (HBASE-4132) Extend the WALObserver API to accomodate log archival

[ https://issues.apache.org/jira/browse/HBASE-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070095#comment-13070095 ] stack commented on HBASE-4132: -- +1 on patch. We could put it into a 0.90.5 if wanted since

[jira] [Commented] (HBASE-4131) Make the Replication Service pluggable via a standard interface definition

[ https://issues.apache.org/jira/browse/HBASE-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070096#comment-13070096 ] stack commented on HBASE-4131: -- This looks fine. How will replicateLogEntries work? The

[jira] [Commented] (HBASE-4132) Extend the WALObserver API to accomodate log archival

[ https://issues.apache.org/jira/browse/HBASE-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070097#comment-13070097 ] stack commented on HBASE-4132: -- There is also master/LogCleaner.java. You know about that?

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

[ https://issues.apache.org/jira/browse/HBASE-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070098#comment-13070098 ] stack commented on HBASE-4120: -- @Liu Thank you for posting the documents. That helps a lot.

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

[ https://issues.apache.org/jira/browse/HBASE-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070102#comment-13070102 ] Andrew Purtell commented on HBASE-4120: --- It would be interesting what can be added

[jira] [Commented] (HBASE-3741) Make HRegionServer aware of the regions it's opening/closing

[ https://issues.apache.org/jira/browse/HBASE-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070101#comment-13070101 ] stack commented on HBASE-3741: -- Question: Looking at this patch again, if we throw a

[jira] [Commented] (HBASE-4124) ZK restarted while assigning a region, new active HM re-assign it but the RS warned 'already online on this server'.

[ https://issues.apache.org/jira/browse/HBASE-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070103#comment-13070103 ] stack commented on HBASE-4124: -- hbase-3741 changes the behavior here in that now we notice if

[jira] [Commented] (HBASE-3872) Hole in split transaction rollback; edits to .META. need to be rolled back even if it seems like they didn't make it

[ https://issues.apache.org/jira/browse/HBASE-3872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070104#comment-13070104 ] Hudson commented on HBASE-3872: --- Integrated in HBase-TRUNK #2049 (See

[jira] [Commented] (HBASE-4129) hbase-3872 added a warn message 'CatalogJanitor: Daughter regiondir does not exist' that is triggered though its often legit that daughter is not present

[ https://issues.apache.org/jira/browse/HBASE-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070105#comment-13070105 ] Hudson commented on HBASE-4129: --- Integrated in HBase-TRUNK #2049 (See

[jira] [Commented] (HBASE-4064) Two concurrent unassigning of the same region caused the endless loop of Region has been PENDING_CLOSE for too long...

[ https://issues.apache.org/jira/browse/HBASE-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070106#comment-13070106 ] stack commented on HBASE-4064: -- bq. 4.When master receives the watcher event, It removes the

[jira] [Commented] (HBASE-4132) Extend the WALObserver API to accomodate log archival

[ https://issues.apache.org/jira/browse/HBASE-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070107#comment-13070107 ] dhruba borthakur commented on HBASE-4132: - stack: I did not even know the

[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-tabpanelfocusedCommentId=13070108#comment-13070108 ] jirapos...@reviews.apache.org commented on HBASE-3899: --

[jira] [Updated] (HBASE-3465) Hbase should use a HADOOP_HOME environment variable if available.

[ https://issues.apache.org/jira/browse/HBASE-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-3465: - Resolution: Fixed Release Note: If HADOOP_HOME is defined, we'll use this hadoop over whats in

[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-tabpanelfocusedCommentId=13070110#comment-13070110 ] stack commented on HBASE-3918: -- bq. So my query is, is this defect applicable only between