[jira] [Commented] (HBASE-20884) Replace usage of our Base64 implementation with java.util.Base64

[ https://issues.apache.org/jira/browse/HBASE-20884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546163#comment-16546163 ] Hudson commented on HBASE-20884: Results for branch branch-1 [build #383 on

[jira] [Commented] (HBASE-18201) add UT and docs for DataBlockEncodingTool

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

[jira] [Commented] (HBASE-20873) Update doc for Endpoint-based Export

[ https://issues.apache.org/jira/browse/HBASE-20873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546188#comment-16546188 ] Chia-Ping Tsai commented on HBASE-20873: {code:java} *endpoint-based Export* +Make sure the

[jira] [Commented] (HBASE-20889) PE scan is failing with NullPointerException

[ https://issues.apache.org/jira/browse/HBASE-20889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546164#comment-16546164 ] Hudson commented on HBASE-20889: Results for branch branch-1 [build #383 on

[jira] [Commented] (HBASE-19893) restore_snapshot is broken in master branch when region splits

[ https://issues.apache.org/jira/browse/HBASE-19893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546170#comment-16546170 ] Ted Yu commented on HBASE-19893: Handling failure of TestRestoreSnapshotFromClientWithRegionReplicas can

[jira] [Commented] (HBASE-20853) Polish "Add defaults to Table Interface so Implementors don't have to"

[ https://issues.apache.org/jira/browse/HBASE-20853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546192#comment-16546192 ] Chia-Ping Tsai commented on HBASE-20853: {code:java} - HTableDescriptor getTableDescriptor()

[jira] [Created] (HBASE-20903) backport HBASE-20792 "info:servername and info:sn inconsistent for OPEN region" to branch-2.0

Allan Yang created HBASE-20903: -- Summary: backport HBASE-20792 "info:servername and info:sn inconsistent for OPEN region" to branch-2.0 Key: HBASE-20903 URL: https://issues.apache.org/jira/browse/HBASE-20903

[jira] [Commented] (HBASE-20883) HMaster Read / Write Requests Per Sec across RegionServers, currently only Total Requests Per Sec

[ https://issues.apache.org/jira/browse/HBASE-20883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546211#comment-16546211 ] Hari Sekhon commented on HBASE-20883: - Ok. Would it hurt to also expose that information in the UI

[jira] [Commented] (HBASE-20792) info:servername and info:sn inconsistent for OPEN region

[ https://issues.apache.org/jira/browse/HBASE-20792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546212#comment-16546212 ] Allan Yang commented on HBASE-20792: As disscussed in HBASE-20864, we should backport this to

[jira] [Commented] (HBASE-20893) Data loss if splitting region while ServerCrashProcedure executing

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

[jira] [Updated] (HBASE-20902) when WAL sync failed, we should bypass the failed DN that previously used

[ https://issues.apache.org/jira/browse/HBASE-20902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenxu updated HBASE-20902: --- Description: in our prod env, there happened to be a slow DN, all WAL#sync with that DN are failed, 

[jira] [Created] (HBASE-20902) when WAL sync failed, we should bypass the failed DN that previously used

chenxu created HBASE-20902: -- Summary: when WAL sync failed, we should bypass the failed DN that previously used Key: HBASE-20902 URL: https://issues.apache.org/jira/browse/HBASE-20902 Project: HBase

[jira] [Commented] (HBASE-19893) restore_snapshot is broken in master branch when region splits

[ https://issues.apache.org/jira/browse/HBASE-19893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546111#comment-16546111 ] Toshihiro Suzuki commented on HBASE-19893: -- I analyzed the test failure of

[jira] [Commented] (HBASE-20902) when WAL sync failed, we should bypass the failed DN that previously used

[ https://issues.apache.org/jira/browse/HBASE-20902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546110#comment-16546110 ] chenxu commented on HBASE-20902: [~Apache9] FYI > when WAL sync failed, we should bypass the failed DN

[jira] [Commented] (HBASE-20901) Reducing region replica has no effect

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

[jira] [Comment Edited] (HBASE-20864) RS was killed due to master thought the region should be on a already dead server

[ https://issues.apache.org/jira/browse/HBASE-20864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546123#comment-16546123 ] Allan Yang edited comment on HBASE-20864 at 7/17/18 7:23 AM: - [~Apache9],

[jira] [Commented] (HBASE-20864) RS was killed due to master thought the region should be on a already dead server

[ https://issues.apache.org/jira/browse/HBASE-20864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546144#comment-16546144 ] Duo Zhang commented on HBASE-20864: --- What HBASE-20792 fixed is that, the lastHost is not a stable one

[jira] [Commented] (HBASE-20864) RS was killed due to master thought the region should be on a already dead server

[ https://issues.apache.org/jira/browse/HBASE-20864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546154#comment-16546154 ] Allan Yang commented on HBASE-20864: I got your point, will not change the semantics. Yes,

[jira] [Updated] (HBASE-19893) restore_snapshot is broken in master branch when region splits

[ https://issues.apache.org/jira/browse/HBASE-19893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki updated HBASE-19893: - Attachment:

[jira] [Commented] (HBASE-20855) PeerConfigTracker only support one listener will cause problem when there is a recovered replication queue

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

[jira] [Comment Edited] (HBASE-19893) restore_snapshot is broken in master branch when region splits

[ https://issues.apache.org/jira/browse/HBASE-19893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546122#comment-16546122 ] Toshihiro Suzuki edited comment on HBASE-19893 at 7/17/18 7:13 AM: ---

[jira] [Commented] (HBASE-19893) restore_snapshot is broken in master branch when region splits

[ https://issues.apache.org/jira/browse/HBASE-19893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546122#comment-16546122 ] Toshihiro Suzuki commented on HBASE-19893: -- One thing, according to the log, it looks like one

[jira] [Commented] (HBASE-20864) RS was killed due to master thought the region should be on a already dead server

[ https://issues.apache.org/jira/browse/HBASE-20864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546123#comment-16546123 ] Allan Yang commented on HBASE-20864: [~Apache9], IIRC, info:sn is used for last host and info:server

[jira] [Commented] (HBASE-20893) Data loss if splitting region while ServerCrashProcedure executing

[ https://issues.apache.org/jira/browse/HBASE-20893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546132#comment-16546132 ] Duo Zhang commented on HBASE-20893: --- Will take a look soon. > Data loss if splitting region while

[jira] [Comment Edited] (HBASE-20864) RS was killed due to master thought the region should be on a already dead server

[ https://issues.apache.org/jira/browse/HBASE-20864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546138#comment-16546138 ] Allan Yang edited comment on HBASE-20864 at 7/17/18 7:34 AM: - It is very

[jira] [Commented] (HBASE-20864) RS was killed due to master thought the region should be on a already dead server

[ https://issues.apache.org/jira/browse/HBASE-20864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546148#comment-16546148 ] Duo Zhang commented on HBASE-20864: --- Oh, seems I misread the comment. Please backport HBASE-20792 to

[jira] [Updated] (HBASE-20855) PeerConfigTracker only support one listener will cause problem when there is a recovered replication queue

[ https://issues.apache.org/jira/browse/HBASE-20855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingyun Tian updated HBASE-20855: - Attachment: HBASE-20855.branch-1.005.patch > PeerConfigTracker only support one listener will

[jira] [Commented] (HBASE-20867) RS may get killed while master restarts

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

[jira] [Updated] (HBASE-20902) when WAL sync failed, we should bypass the failed DN that previously used

[ https://issues.apache.org/jira/browse/HBASE-20902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenxu updated HBASE-20902: --- Attachment: HBASE-20902-master-v1.patch > when WAL sync failed, we should bypass the failed DN that

[jira] [Commented] (HBASE-19893) restore_snapshot is broken in master branch when region splits

[ https://issues.apache.org/jira/browse/HBASE-19893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546113#comment-16546113 ] Toshihiro Suzuki commented on HBASE-19893: -- I just re-uploaded the latest patch to run QA

[jira] [Updated] (HBASE-19893) restore_snapshot is broken in master branch when region splits

[ https://issues.apache.org/jira/browse/HBASE-19893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki updated HBASE-19893: - Attachment: HBASE-19893.master.005.patch > restore_snapshot is broken in master branch

[jira] [Comment Edited] (HBASE-20864) RS was killed due to master thought the region should be on a already dead server

[ https://issues.apache.org/jira/browse/HBASE-20864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546123#comment-16546123 ] Allan Yang edited comment on HBASE-20864 at 7/17/18 7:15 AM: - [~Apache9],

[jira] [Commented] (HBASE-20864) RS was killed due to master thought the region should be on a already dead server

[ https://issues.apache.org/jira/browse/HBASE-20864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546129#comment-16546129 ] Duo Zhang commented on HBASE-20864: --- This is a bit confusing but info:sn is not used for last host, it

[jira] [Commented] (HBASE-20893) Data loss if splitting region while ServerCrashProcedure executing

[ https://issues.apache.org/jira/browse/HBASE-20893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546131#comment-16546131 ] Allan Yang commented on HBASE-20893: [~Apache9], can you review this one? > Data loss if splitting

[jira] [Commented] (HBASE-20864) RS was killed due to master thought the region should be on a already dead server

[ https://issues.apache.org/jira/browse/HBASE-20864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546138#comment-16546138 ] Allan Yang commented on HBASE-20864: It is very confusing that master takes info:server as last host

[jira] [Comment Edited] (HBASE-20864) RS was killed due to master thought the region should be on a already dead server

[ https://issues.apache.org/jira/browse/HBASE-20864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546138#comment-16546138 ] Allan Yang edited comment on HBASE-20864 at 7/17/18 7:31 AM: - It is very

[jira] [Commented] (HBASE-20864) RS was killed due to master thought the region should be on a already dead server

[ https://issues.apache.org/jira/browse/HBASE-20864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546142#comment-16546142 ] Duo Zhang commented on HBASE-20864: --- Please do not change to use info:servername as the current

[jira] [Commented] (HBASE-20893) Data loss if splitting region while ServerCrashProcedure executing

[ https://issues.apache.org/jira/browse/HBASE-20893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546146#comment-16546146 ] Allan Yang commented on HBASE-20893: This one should commit first, and then I will change

[jira] [Commented] (HBASE-20855) PeerConfigTracker only support one listener will cause problem when there is a recovered replication queue

[ https://issues.apache.org/jira/browse/HBASE-20855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546462#comment-16546462 ] Jingyun Tian commented on HBASE-20855: -- [~yuzhih...@gmail.com] Test failed due to following reason.

[jira] [Updated] (HBASE-20855) PeerConfigTracker only support one listener will cause problem when there is a recovered replication queue

[ https://issues.apache.org/jira/browse/HBASE-20855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingyun Tian updated HBASE-20855: - Attachment: (was: HBASE-20855.branch-1.005.patch) > PeerConfigTracker only support one

[jira] [Updated] (HBASE-20855) PeerConfigTracker only support one listener will cause problem when there is a recovered replication queue

[ https://issues.apache.org/jira/browse/HBASE-20855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingyun Tian updated HBASE-20855: - Attachment: HBASE-20855.branch-1.005.patch > PeerConfigTracker only support one listener will

[jira] [Updated] (HBASE-18659) Use HDFS ACL to give user the ability to read snapshot directly on HDFS

[ https://issues.apache.org/jira/browse/HBASE-18659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Mei updated HBASE-18659: --- Attachment: HBASE-18659.master.001.patch > Use HDFS ACL to give user the ability to read snapshot directly

[jira] [Commented] (HBASE-20855) PeerConfigTracker only support one listener will cause problem when there is a recovered replication queue

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

[jira] [Updated] (HBASE-18659) Use HDFS ACL to give user the ability to read snapshot directly on HDFS

[ https://issues.apache.org/jira/browse/HBASE-18659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Mei updated HBASE-18659: --- Attachment: HBASE-18659.master.002.patch > Use HDFS ACL to give user the ability to read snapshot directly

[jira] [Updated] (HBASE-18659) Use HDFS ACL to give user the ability to read snapshot directly on HDFS

[ https://issues.apache.org/jira/browse/HBASE-18659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Mei updated HBASE-18659: --- Attachment: HBASE-18659.master.003.patch > Use HDFS ACL to give user the ability to read snapshot directly

[jira] [Commented] (HBASE-20855) PeerConfigTracker only support one listener will cause problem when there is a recovered replication queue

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

[jira] [Commented] (HBASE-13984) Add option to allow caller to know the heartbeat and scanner position when scanner timeout

[ https://issues.apache.org/jira/browse/HBASE-13984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546243#comment-16546243 ] Minwoo Kang commented on HBASE-13984: - I wonder why this issue status is still PATCH AVAILABLE. >

[jira] [Updated] (HBASE-20855) PeerConfigTracker only support one listener will cause problem when there is a recovered replication queue

[ https://issues.apache.org/jira/browse/HBASE-20855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingyun Tian updated HBASE-20855: - Attachment: HBASE-20855.branch-1.005.patch > PeerConfigTracker only support one listener will

[jira] [Updated] (HBASE-20855) PeerConfigTracker only support one listener will cause problem when there is a recovered replication queue

[ https://issues.apache.org/jira/browse/HBASE-20855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingyun Tian updated HBASE-20855: - Attachment: (was: HBASE-20855.branch-1.005.patch) > PeerConfigTracker only support one

[jira] [Updated] (HBASE-20870) Wrong HBase root dir in ITBLL's Search Tool

[ https://issues.apache.org/jira/browse/HBASE-20870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allan Yang updated HBASE-20870: --- Attachment: HBASE-20870.branch-2.0.003.patch > Wrong HBase root dir in ITBLL's Search Tool >

[jira] [Updated] (HBASE-20855) PeerConfigTracker only support one listener will cause problem when there is a recovered replication queue

[ https://issues.apache.org/jira/browse/HBASE-20855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingyun Tian updated HBASE-20855: - Attachment: (was: HBASE-20855.branch-1.005.patch) > PeerConfigTracker only support one

[jira] [Updated] (HBASE-20855) PeerConfigTracker only support one listener will cause problem when there is a recovered replication queue

[ https://issues.apache.org/jira/browse/HBASE-20855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingyun Tian updated HBASE-20855: - Attachment: HBASE-20855.branch-1.005.patch > PeerConfigTracker only support one listener will

[jira] [Commented] (HBASE-20860) Merged region's RIT state may not be cleaned after master restart

[ https://issues.apache.org/jira/browse/HBASE-20860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546252#comment-16546252 ] Allan Yang commented on HBASE-20860: {quote} Please also push it to branch-2? {quote} Sure,

[jira] [Assigned] (HBASE-18659) Use HDFS ACL to give user the ability to read snapshot directly on HDFS

[ https://issues.apache.org/jira/browse/HBASE-18659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Mei reassigned HBASE-18659: -- Assignee: Yi Mei > Use HDFS ACL to give user the ability to read snapshot directly on HDFS >

[jira] [Commented] (HBASE-13984) Add option to allow caller to know the heartbeat and scanner position when scanner timeout

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

[jira] [Commented] (HBASE-20855) PeerConfigTracker only support one listener will cause problem when there is a recovered replication queue

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

[jira] [Updated] (HBASE-20870) Wrong HBase root dir in ITBLL's Search Tool

[ https://issues.apache.org/jira/browse/HBASE-20870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allan Yang updated HBASE-20870: --- Attachment: HBASE-20870.branch-2.0.003.patch > Wrong HBase root dir in ITBLL's Search Tool >

[jira] [Updated] (HBASE-20870) Wrong HBase root dir in ITBLL's Search Tool

[ https://issues.apache.org/jira/browse/HBASE-20870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allan Yang updated HBASE-20870: --- Attachment: (was: HBASE-20870.branch-2.0.003.patch) > Wrong HBase root dir in ITBLL's Search

<    1   2