[jira] [Commented] (HBASE-15221) HTableMultiplexer improvements (stale region locations and resource leaks)

[ https://issues.apache.org/jira/browse/HBASE-15221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144266#comment-15144266 ] Hudson commented on HBASE-15221: FAILURE: Integrated in HBase-1.1-JDK7 #1661 (See

[jira] [Commented] (HBASE-15198) RPC client not using Codec and CellBlock for puts by default

[ https://issues.apache.org/jira/browse/HBASE-15198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144254#comment-15144254 ] Hudson commented on HBASE-15198: FAILURE: Integrated in HBase-Trunk_matrix #703 (See

[jira] [Commented] (HBASE-15205) Do not find the replication scope for every WAL#append()

[ https://issues.apache.org/jira/browse/HBASE-15205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144359#comment-15144359 ] Hadoop QA commented on HBASE-15205: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-15120) Backport HBASE-14883 to branch-1.1

[ https://issues.apache.org/jira/browse/HBASE-15120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144365#comment-15144365 ] Hadoop QA commented on HBASE-15120: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-15205) Do not find the replication scope for every WAL#append()

[ https://issues.apache.org/jira/browse/HBASE-15205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144278#comment-15144278 ] ramkrishna.s.vasudevan commented on HBASE-15205: bq.Instead we directly set the scope

[jira] [Commented] (HBASE-15205) Do not find the replication scope for every WAL#append()

[ https://issues.apache.org/jira/browse/HBASE-15205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144302#comment-15144302 ] ramkrishna.s.vasudevan commented on HBASE-15205: bq.. It is configurable with

[jira] [Updated] (HBASE-15205) Do not find the replication scope for every WAL#append()

[ https://issues.apache.org/jira/browse/HBASE-15205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-15205: --- Status: Patch Available (was: Open) > Do not find the replication scope for

[jira] [Assigned] (HBASE-15259) WALEdits under replay will also be replicated

[ https://issues.apache.org/jira/browse/HBASE-15259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan reassigned HBASE-15259: -- Assignee: ramkrishna.s.vasudevan > WALEdits under replay will also be

[jira] [Commented] (HBASE-15259) WALEdits under replay will also be replicated

[ https://issues.apache.org/jira/browse/HBASE-15259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144280#comment-15144280 ] ramkrishna.s.vasudevan commented on HBASE-15259: [~enis] Have you observed any time Edits

[jira] [Commented] (HBASE-14866) VerifyReplication should use peer configuration in peer connection

[ https://issues.apache.org/jira/browse/HBASE-14866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144353#comment-15144353 ] Ashish Singhi commented on HBASE-14866: --- [~ghelmling], can you please add a release note for this

[jira] [Commented] (HBASE-15254) Support fixed domain name in Kerberos name for HBase replication cross realm trust setup

[ https://issues.apache.org/jira/browse/HBASE-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144348#comment-15144348 ] Ashish Singhi commented on HBASE-15254: --- Thanks [~ghelmling] for pointing to HBASE-14866. Actually

[jira] [Updated] (HBASE-15252) Data loss when replaying wal if HDFS timeout

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

[jira] [Commented] (HBASE-15205) Do not find the replication scope for every WAL#append()

[ https://issues.apache.org/jira/browse/HBASE-15205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144298#comment-15144298 ] Ashish Singhi commented on HBASE-15205: --- bq. For which we have to disable and enable the table. So

[jira] [Commented] (HBASE-15205) Do not find the replication scope for every WAL#append()

[ https://issues.apache.org/jira/browse/HBASE-15205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144529#comment-15144529 ] Ted Yu commented on HBASE-15205: lgtm {code} 711 NavigableMap getScopes(); {code}

[jira] [Resolved] (HBASE-15252) Data loss when replaying wal if HDFS timeout

[ https://issues.apache.org/jira/browse/HBASE-15252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-15252. --- Resolution: Fixed Pushed the addendum to 0.98. > Data loss when replaying wal if HDFS timeout >

[jira] [Commented] (HBASE-15252) Data loss when replaying wal if HDFS timeout

[ https://issues.apache.org/jira/browse/HBASE-15252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144496#comment-15144496 ] Hudson commented on HBASE-15252: SUCCESS: Integrated in HBase-1.2-IT #434 (See

[jira] [Updated] (HBASE-15252) Data loss when replaying wal if HDFS timeout

[ https://issues.apache.org/jira/browse/HBASE-15252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-15252: -- Attachment: HBASE-15252-addendum-0.98.patch Fix compile error for 0.98 on hadoop-1.1 > Data loss when

[jira] [Commented] (HBASE-15169) Backport HBASE-14362 'TestWALProcedureStoreOnHDFS is super duper flaky' to branch-1.1

[ https://issues.apache.org/jira/browse/HBASE-15169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144408#comment-15144408 ] Hadoop QA commented on HBASE-15169: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-15245) Port HBASE-15177 (Reduce garbage created under high load) to 0.98

[ https://issues.apache.org/jira/browse/HBASE-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144523#comment-15144523 ] Hudson commented on HBASE-15245: FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #1171 (See

[jira] [Commented] (HBASE-15252) Data loss when replaying wal if HDFS timeout

[ https://issues.apache.org/jira/browse/HBASE-15252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144521#comment-15144521 ] Hudson commented on HBASE-15252: FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #1171 (See

[jira] [Commented] (HBASE-15177) Reduce garbage created under high load

[ https://issues.apache.org/jira/browse/HBASE-15177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144522#comment-15144522 ] Hudson commented on HBASE-15177: FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #1171 (See

[jira] [Commented] (HBASE-15205) Do not find the replication scope for every WAL#append()

[ https://issues.apache.org/jira/browse/HBASE-15205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144532#comment-15144532 ] Anoop Sam John commented on HBASE-15205: {code} Set families =

[jira] [Commented] (HBASE-15252) Data loss when replaying wal if HDFS timeout

[ https://issues.apache.org/jira/browse/HBASE-15252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144482#comment-15144482 ] Hudson commented on HBASE-15252: FAILURE: Integrated in HBase-Trunk_matrix #704 (See

[jira] [Updated] (HBASE-15205) Do not find the replication scope for every WAL#append()

[ https://issues.apache.org/jira/browse/HBASE-15205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-15205: --- Status: Patch Available (was: Open) > Do not find the replication scope for

[jira] [Updated] (HBASE-15205) Do not find the replication scope for every WAL#append()

[ https://issues.apache.org/jira/browse/HBASE-15205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-15205: --- Status: Open (was: Patch Available) > Do not find the replication scope for

[jira] [Updated] (HBASE-15205) Do not find the replication scope for every WAL#append()

[ https://issues.apache.org/jira/browse/HBASE-15205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-15205: --- Attachment: HBASE-15205_2.patch Updated patch. Corrects the checkstyle and

[jira] [Reopened] (HBASE-15252) Data loss when replaying wal if HDFS timeout

[ https://issues.apache.org/jira/browse/HBASE-15252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reopened HBASE-15252: --- The patch for 0.98 breaks hadoop-1.1 compatibility. > Data loss when replaying wal if HDFS timeout >

[jira] [Updated] (HBASE-14949) Resolve name conflict when splitting if there are duplicated WAL entries

[ https://issues.apache.org/jira/browse/HBASE-14949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-14949: -- Parent Issue: HBASE-14790 (was: HBASE-14004) > Resolve name conflict when splitting if there are

[jira] [Commented] (HBASE-15252) Data loss when replaying wal if HDFS timeout

[ https://issues.apache.org/jira/browse/HBASE-15252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144605#comment-15144605 ] Hudson commented on HBASE-15252: SUCCESS: Integrated in HBase-1.2 #546 (See

[jira] [Commented] (HBASE-15252) Data loss when replaying wal if HDFS timeout

[ https://issues.apache.org/jira/browse/HBASE-15252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144668#comment-15144668 ] Hudson commented on HBASE-15252: SUCCESS: Integrated in HBase-1.3-IT #499 (See

[jira] [Updated] (HBASE-14949) Resolve name conflict when splitting if there are duplicated WAL entries

[ https://issues.apache.org/jira/browse/HBASE-14949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-14949: -- Attachment: HBASE-14949-v3.patch New patch solve the name conflict when split. > Resolve name

[jira] [Assigned] (HBASE-14949) Resolve name conflict when splitting if there are duplicated WAL entries

[ https://issues.apache.org/jira/browse/HBASE-14949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reassigned HBASE-14949: - Assignee: Duo Zhang > Resolve name conflict when splitting if there are duplicated WAL entries

[jira] [Commented] (HBASE-15219) Canary tool does not return non-zero exit code when one of regions is in stuck state

[ https://issues.apache.org/jira/browse/HBASE-15219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144640#comment-15144640 ] Maddineni Sukumar commented on HBASE-15219: --- I tried below simple scenario and tool is not

[jira] [Updated] (HBASE-14949) Resolve name conflict when splitting if there are duplicated WAL entries

[ https://issues.apache.org/jira/browse/HBASE-14949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-14949: -- Summary: Resolve name conflict when splitting if there are duplicated WAL entries (was: Skip

[jira] [Commented] (HBASE-15252) Data loss when replaying wal if HDFS timeout

[ https://issues.apache.org/jira/browse/HBASE-15252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144613#comment-15144613 ] stack commented on HBASE-15252: --- Thanks [~Apache9] > Data loss when replaying wal if HDFS timeout >

[jira] [Commented] (HBASE-15252) Data loss when replaying wal if HDFS timeout

[ https://issues.apache.org/jira/browse/HBASE-15252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144630#comment-15144630 ] Hudson commented on HBASE-15252: FAILURE: Integrated in HBase-1.3 #552 (See

[jira] [Updated] (HBASE-15205) Do not find the replication scope for every WAL#append()

[ https://issues.apache.org/jira/browse/HBASE-15205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-15205: --- Attachment: HBASE-15205_1.patch This patch does the following -> collects

[jira] [Commented] (HBASE-15129) Set default value for hbase.fs.tmp.dir rather than fully depend on hbase-default.xml

[ https://issues.apache.org/jira/browse/HBASE-15129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144852#comment-15144852 ] Hudson commented on HBASE-15129: FAILURE: Integrated in HBase-1.0 #1145 (See

[jira] [Commented] (HBASE-15252) Data loss when replaying wal if HDFS timeout

[ https://issues.apache.org/jira/browse/HBASE-15252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144851#comment-15144851 ] Hudson commented on HBASE-15252: FAILURE: Integrated in HBase-1.0 #1145 (See

[jira] [Commented] (HBASE-14812) Fix ResultBoundedCompletionService deadlock

[ https://issues.apache.org/jira/browse/HBASE-14812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144886#comment-15144886 ] Hudson commented on HBASE-14812: FAILURE: Integrated in HBase-1.1-JDK7 #1662 (See

[jira] [Commented] (HBASE-15252) Data loss when replaying wal if HDFS timeout

[ https://issues.apache.org/jira/browse/HBASE-15252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144885#comment-15144885 ] Hudson commented on HBASE-15252: FAILURE: Integrated in HBase-1.1-JDK7 #1662 (See

[jira] [Commented] (HBASE-15245) Port HBASE-15177 (Reduce garbage created under high load) to 0.98

[ https://issues.apache.org/jira/browse/HBASE-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144900#comment-15144900 ] Hudson commented on HBASE-15245: FAILURE: Integrated in HBase-0.98-matrix #297 (See

[jira] [Commented] (HBASE-15252) Data loss when replaying wal if HDFS timeout

[ https://issues.apache.org/jira/browse/HBASE-15252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144898#comment-15144898 ] Hudson commented on HBASE-15252: FAILURE: Integrated in HBase-0.98-matrix #297 (See

[jira] [Commented] (HBASE-15177) Reduce garbage created under high load

[ https://issues.apache.org/jira/browse/HBASE-15177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144899#comment-15144899 ] Hudson commented on HBASE-15177: FAILURE: Integrated in HBase-0.98-matrix #297 (See

[jira] [Commented] (HBASE-15219) Canary tool does not return non-zero exit code when one of regions is in stuck state

[ https://issues.apache.org/jira/browse/HBASE-15219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144905#comment-15144905 ] Ted Yu commented on HBASE-15219: [~sukuna...@gmail.com]: This is not in any hbase release yet. Can you

[jira] [Reopened] (HBASE-15219) Canary tool does not return non-zero exit code when one of regions is in stuck state

[ https://issues.apache.org/jira/browse/HBASE-15219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell reopened HBASE-15219: This wasn't tested? > Canary tool does not return non-zero exit code when one of regions is

[jira] [Commented] (HBASE-15205) Do not find the replication scope for every WAL#append()

[ https://issues.apache.org/jira/browse/HBASE-15205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144741#comment-15144741 ] Hadoop QA commented on HBASE-15205: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-15252) Data loss when replaying wal if HDFS timeout

[ https://issues.apache.org/jira/browse/HBASE-15252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144771#comment-15144771 ] Hudson commented on HBASE-15252: SUCCESS: Integrated in HBase-1.1-JDK8 #1749 (See

[jira] [Commented] (HBASE-14812) Fix ResultBoundedCompletionService deadlock

[ https://issues.apache.org/jira/browse/HBASE-14812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144772#comment-15144772 ] Hudson commented on HBASE-14812: SUCCESS: Integrated in HBase-1.1-JDK8 #1749 (See

[jira] [Commented] (HBASE-15254) Support fixed domain name in Kerberos name for HBase replication cross realm trust setup

[ https://issues.apache.org/jira/browse/HBASE-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144794#comment-15144794 ] Ashish Singhi commented on HBASE-15254: --- Our idea to handle this issue was (similar to how Hadoop

[jira] [Updated] (HBASE-15260) Should we check zero length value in checkAndMutate when null is passes as expected value?

[ https://issues.apache.org/jira/browse/HBASE-15260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated HBASE-15260: -- Description: Should we check zero length value in checkAndMutate when null is passes as

[jira] [Commented] (HBASE-15260) Should we check zero length value in checkAndMutate when null is passes as expected value?

[ https://issues.apache.org/jira/browse/HBASE-15260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145019#comment-15145019 ] Ankit Singhal commented on HBASE-15260: --- [~anoopsamjohn], but there is also a zero length check on

[jira] [Commented] (HBASE-15254) Support fixed domain name in Kerberos name for HBase replication cross realm trust setup

[ https://issues.apache.org/jira/browse/HBASE-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144927#comment-15144927 ] Gary Helmling commented on HBASE-15254: --- bq. We simply ran the command add_peer '1',

[jira] [Commented] (HBASE-15260) Should we check zero length value in checkAndMutate when null is passes as expected value?

[ https://issues.apache.org/jira/browse/HBASE-15260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144932#comment-15144932 ] Anoop Sam John commented on HBASE-15260: null should be checked for the lack of column IMO. The

[jira] [Created] (HBASE-15260) Should we check zero length value in checkAndMutate when null is passes as expected value?

Ankit Singhal created HBASE-15260: - Summary: Should we check zero length value in checkAndMutate when null is passes as expected value? Key: HBASE-15260 URL: https://issues.apache.org/jira/browse/HBASE-15260

[jira] [Commented] (HBASE-14949) Resolve name conflict when splitting if there are duplicated WAL entries

[ https://issues.apache.org/jira/browse/HBASE-14949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145131#comment-15145131 ] Hadoop QA commented on HBASE-14949: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-15240) Go Big BucketCache Fixes

[ https://issues.apache.org/jira/browse/HBASE-15240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145151#comment-15145151 ] stack commented on HBASE-15240: --- Messing some more, prefetch needs the above hack where we wait to get our

[jira] [Commented] (HBASE-6721) RegionServer Group based Assignment

[ https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145843#comment-15145843 ] Elliott Clark commented on HBASE-6721: -- bq.Took a quick look at how the NN publishes metadata via

[jira] [Commented] (HBASE-15232) Exceptions returned over multi RPC don't automatically trigger region location reloads

[ https://issues.apache.org/jira/browse/HBASE-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145854#comment-15145854 ] Elliott Clark commented on HBASE-15232: --- lgtm > Exceptions returned over multi RPC don't

[jira] [Commented] (HBASE-15079) TestMultiParallel.validateLoadedData AssertionError: null

[ https://issues.apache.org/jira/browse/HBASE-15079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145792#comment-15145792 ] Anoop Sam John commented on HBASE-15079: The backport of this Jira to 0.98 branch broke one test

[jira] [Reopened] (HBASE-15079) TestMultiParallel.validateLoadedData AssertionError: null

[ https://issues.apache.org/jira/browse/HBASE-15079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John reopened HBASE-15079: Reopening as I see test failures after commit of this Jira to 0.98 (No other fix branches have

[jira] [Commented] (HBASE-15251) During a cluster restart, Hmaster thinks it is a failover by mistake

[ https://issues.apache.org/jira/browse/HBASE-15251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145810#comment-15145810 ] Stephen Yuan Jiang commented on HBASE-15251: [~claraxiong], please upload the updated the

[jira] [Resolved] (HBASE-15079) TestMultiParallel.validateLoadedData AssertionError: null

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

[jira] [Commented] (HBASE-15251) During a cluster restart, Hmaster thinks it is a failover by mistake

[ https://issues.apache.org/jira/browse/HBASE-15251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145814#comment-15145814 ] Stephen Yuan Jiang commented on HBASE-15251: I asked the performance gain is because that it

[jira] [Commented] (HBASE-15259) WALEdits under replay will also be replicated

[ https://issues.apache.org/jira/browse/HBASE-15259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145785#comment-15145785 ] Anoop Sam John commented on HBASE-15259: On a first go over the code, it looks to be problematic

[jira] [Commented] (HBASE-15079) TestMultiParallel.validateLoadedData AssertionError: null

[ https://issues.apache.org/jira/browse/HBASE-15079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145858#comment-15145858 ] Andrew Purtell commented on HBASE-15079: Sure thing > TestMultiParallel.validateLoadedData

[jira] [Commented] (HBASE-13839) Fix AssgnmentManagerTmpl.jamon issues (coloring, content etc.)

[ https://issues.apache.org/jira/browse/HBASE-13839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145808#comment-15145808 ] Hudson commented on HBASE-13839: FAILURE: Integrated in HBase-Trunk_matrix #706 (See

[jira] [Commented] (HBASE-9393) Hbase does not closing a closed socket resulting in many CLOSE_WAIT

[ https://issues.apache.org/jira/browse/HBASE-9393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145809#comment-15145809 ] Hudson commented on HBASE-9393: --- FAILURE: Integrated in HBase-Trunk_matrix #706 (See

[jira] [Commented] (HBASE-15219) Canary tool does not return non-zero exit code when one of regions is in stuck state

[ https://issues.apache.org/jira/browse/HBASE-15219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145836#comment-15145836 ] Maddineni Sukumar commented on HBASE-15219: --- Thanks [~ted_yu] . We applied this patch on

[jira] [Commented] (HBASE-15229) Canary Tools should not call System.Exit on error

[ https://issues.apache.org/jira/browse/HBASE-15229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145290#comment-15145290 ] Ted Yu commented on HBASE-15229: This may have resulted in exit code from Canary to always be 0. >

[jira] [Comment Edited] (HBASE-15219) Canary tool does not return non-zero exit code when one of regions is in stuck state

[ https://issues.apache.org/jira/browse/HBASE-15219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144905#comment-15144905 ] Ted Yu edited comment on HBASE-15219 at 2/12/16 8:18 PM: - [~sukuna...@gmail.com]:

[jira] [Commented] (HBASE-15219) Canary tool does not return non-zero exit code when one of regions is in stuck state

[ https://issues.apache.org/jira/browse/HBASE-15219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145250#comment-15145250 ] Ted Yu commented on HBASE-15219: I put the following on top of patch v7: {code} +public boolean

[jira] [Commented] (HBASE-14724) Per column family numops metrics

[ https://issues.apache.org/jira/browse/HBASE-14724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145295#comment-15145295 ] Hadoop QA commented on HBASE-14724: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (HBASE-15232) Exceptions returned over multi RPC don't automatically trigger region location reloads

[ https://issues.apache.org/jira/browse/HBASE-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145423#comment-15145423 ] Josh Elser commented on HBASE-15232: Oh, it's {{ClientExceptionsUtil}}. Took me a moment :) Thanks

[jira] [Updated] (HBASE-14724) Per column family numops metrics

[ https://issues.apache.org/jira/browse/HBASE-14724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashu Pachauri updated HBASE-14724: -- Attachment: HBASE-14724-3.patch V3: Adjusted Fixed Heap overhead in HRegion.java to fix the

[jira] [Commented] (HBASE-6721) RegionServer Group based Assignment

[ https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145474#comment-15145474 ] stack commented on HBASE-6721: -- [~eclark] if was in a separate module and feature name was changed to not be

[jira] [Commented] (HBASE-15240) Go Big BucketCache Fixes

[ https://issues.apache.org/jira/browse/HBASE-15240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145477#comment-15145477 ] Andrew Purtell commented on HBASE-15240: And best effort / background fetch is intended, so even

[jira] [Updated] (HBASE-13839) Fix AssgnmentManagerTmpl.jamon issues (coloring, content etc.)

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

[jira] [Commented] (HBASE-15219) Canary tool does not return non-zero exit code when one of regions is in stuck state

[ https://issues.apache.org/jira/browse/HBASE-15219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145541#comment-15145541 ] Hudson commented on HBASE-15219: FAILURE: Integrated in HBase-1.3 #554 (See

[jira] [Commented] (HBASE-15260) Should we check zero length value in checkAndMutate when null is passes as expected value?

[ https://issues.apache.org/jira/browse/HBASE-15260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145332#comment-15145332 ] stack commented on HBASE-15260: --- What you seeing [~ankit.singhal]? Yeah, a no value is supposed to be legit

[jira] [Created] (HBASE-15261) Make Throwable t in DaughterOpener volatile

huaxiang sun created HBASE-15261: Summary: Make Throwable t in DaughterOpener volatile Key: HBASE-15261 URL: https://issues.apache.org/jira/browse/HBASE-15261 Project: HBase Issue Type: Bug

[jira] [Updated] (HBASE-15232) Exceptions returned over multi RPC don't automatically trigger region location reloads

[ https://issues.apache.org/jira/browse/HBASE-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated HBASE-15232: --- Attachment: HBASE-15232.002.patch .002 Rebased on master, and tries to address Elliott's feedback.

[jira] [Commented] (HBASE-6721) RegionServer Group based Assignment

[ https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145253#comment-15145253 ] Matteo Bertozzi commented on HBASE-6721: just gave a look at the patch. most of the code seems

[jira] [Commented] (HBASE-9393) Hbase does not closing a closed socket resulting in many CLOSE_WAIT

[ https://issues.apache.org/jira/browse/HBASE-9393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145361#comment-15145361 ] stack commented on HBASE-9393: -- I tried to backport to branch-1 but doesn't apply cleanly. > Hbase does not

[jira] [Updated] (HBASE-9393) Hbase does not closing a closed socket resulting in many CLOSE_WAIT

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

[jira] [Commented] (HBASE-15240) Go Big BucketCache Fixes

[ https://issues.apache.org/jira/browse/HBASE-15240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145468#comment-15145468 ] Andrew Purtell commented on HBASE-15240: Not saying it shouldn't be improved, but prefetch is

[jira] [Commented] (HBASE-15232) Exceptions returned over multi RPC don't automatically trigger region location reloads

[ https://issues.apache.org/jira/browse/HBASE-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145484#comment-15145484 ] Josh Elser commented on HBASE-15232: Ok! Thanks for clarifying. Looks like maybe ClientExceptionUtils

[jira] [Commented] (HBASE-15240) Go Big BucketCache Fixes

[ https://issues.apache.org/jira/browse/HBASE-15240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145499#comment-15145499 ] stack commented on HBASE-15240: --- bq. Not saying it shouldn't be improved, but prefetch is only supposed to

[jira] [Commented] (HBASE-15219) Canary tool does not return non-zero exit code when one of regions is in stuck state

[ https://issues.apache.org/jira/browse/HBASE-15219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145501#comment-15145501 ] Ted Yu commented on HBASE-15219: This patch was checked in before the one for HBASE-15229. When testing,

[jira] [Commented] (HBASE-15232) Exceptions returned over multi RPC don't automatically trigger region location reloads

[ https://issues.apache.org/jira/browse/HBASE-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145341#comment-15145341 ] stack commented on HBASE-15232: --- Ok. Patch LGTM. > Exceptions returned over multi RPC don't automatically

[jira] [Commented] (HBASE-15219) Canary tool does not return non-zero exit code when one of regions is in stuck state

[ https://issues.apache.org/jira/browse/HBASE-15219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145491#comment-15145491 ] Andrew Purtell commented on HBASE-15219: Retest, Sukumar? > Canary tool does not return non-zero

[jira] [Updated] (HBASE-15261) Make Throwable t in DaughterOpener volatile

[ https://issues.apache.org/jira/browse/HBASE-15261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-15261: - Status: Patch Available (was: Open) > Make Throwable t in DaughterOpener volatile >

[jira] [Updated] (HBASE-15261) Make Throwable t in DaughterOpener volatile

[ https://issues.apache.org/jira/browse/HBASE-15261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-15261: - Attachment: HBASE-15261-001.patch > Make Throwable t in DaughterOpener volatile >

[jira] [Commented] (HBASE-15232) Exceptions returned over multi RPC don't automatically trigger region location reloads

[ https://issues.apache.org/jira/browse/HBASE-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145395#comment-15145395 ] Elliott Clark commented on HBASE-15232: --- -1 Don't clear the cache on multi's if the exception isn't

[jira] [Commented] (HBASE-15260) Should we check zero length value in checkAndMutate when null is passes as expected value?

[ https://issues.apache.org/jira/browse/HBASE-15260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145416#comment-15145416 ] Enis Soztutar commented on HBASE-15260: --- We should differentiate in checkAndXX between byte[0] and

[jira] [Commented] (HBASE-15232) Exceptions returned over multi RPC don't automatically trigger region location reloads

[ https://issues.apache.org/jira/browse/HBASE-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145435#comment-15145435 ] Elliott Clark commented on HBASE-15232: --- Yeah sorry

[jira] [Commented] (HBASE-15240) Go Big BucketCache Fixes

[ https://issues.apache.org/jira/browse/HBASE-15240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145260#comment-15145260 ] stack commented on HBASE-15240: --- Doing quick profile on prefetch -- it takes a long time to load the block

[jira] [Commented] (HBASE-14790) Implement a new DFSOutputStream for logging WAL only

[ https://issues.apache.org/jira/browse/HBASE-14790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145631#comment-15145631 ] Zhe Zhang commented on HBASE-14790: --- Nice work here [~Apache9]. By quickly browsing through the code, I

[jira] [Commented] (HBASE-14724) Per column family numops metrics

[ https://issues.apache.org/jira/browse/HBASE-14724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145638#comment-15145638 ] Ashu Pachauri commented on HBASE-14724: --- The checkstyle errors are related to method length which

[jira] [Updated] (HBASE-9393) Hbase does not closing a closed socket resulting in many CLOSE_WAIT

[ https://issues.apache.org/jira/browse/HBASE-9393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singhi updated HBASE-9393: - Release Note: To handle this issue user need to have Hadoop client 2.6.4 or 2.7.0+ Hadoop

  1   2   >