[jira] [Commented] (HBASE-19102) TestZooKeeperMainServer fails with KeeperException$ConnectionLossException

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241642#comment-16241642
 ] 

Hudson commented on HBASE-19102:


FAILURE: Integrated in Jenkins build HBase-1.4 #999 (See 
[https://builds.apache.org/job/HBase-1.4/999/])
HBASE-19102 TestZooKeeperMainServer fails with KeeperException (stack: rev 
afa1b915098eff226577b17dc3f22d31fe9cd215)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperMainServer.java


> TestZooKeeperMainServer fails with KeeperException$ConnectionLossException
> --
>
> Key: HBASE-19102
> URL: https://issues.apache.org/jira/browse/HBASE-19102
> Project: HBase
>  Issue Type: Bug
>Reporter: stack
>Assignee: stack
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1
>
> Attachments: HBASE-19102.master.001.patch, 
> HBASE-19102.master.002.patch, HBASE-19102.master.002.patch
>
>
> I'm trying to run test suite on a local machine. I never get to the second 
> part because I fail on below test with below exception near every time (and 
> an ipv6 test... will do that next).  
> 1 
> ---
>   2 Test set: org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   3 
> ---
>   4 Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 16.161 s 
> <<< FAILURE! - in org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   5 
> testCommandLineWorks(org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer)
>   Time elapsed: 15.848 s  <<< ERROR!
>   6 org.apache.zookeeper.KeeperException$ConnectionLossException: 
> KeeperErrorCode = ConnectionLoss for /testCommandLineWorks
>   7   at 
> org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer.testCommandLineWorks(TestZooKeeperMainServer.java:81)
> Looks like running the command before we are connected causes the above -- we 
> pause 15 seconds and then throw the above.   If I wait until connected before 
> proceding, stuff seems to work reliably. I don't have access to the watcher 
> on connections since we override the zk main class... so this seems only 
> avenue available at mo (This zk main thing is all a hack around zk main 
> because it had bugs ... but I think we have to keep the hack because folks 
> use different versions of zk. My $workplace defaults to something that is 
> years old, 3.4.5 for instance).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-19009) implement enable/disableTableReplication for AsyncAdmin

[Guanghao Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19009:
---
Attachment: HBASE-19009.master.006.patch

> implement enable/disableTableReplication for AsyncAdmin
> ---
>
> Key: HBASE-19009
> URL: https://issues.apache.org/jira/browse/HBASE-19009
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Fix For: 3.0.0, 2.0.0-beta-1
>
> Attachments: HBASE-19009.master.001.patch, 
> HBASE-19009.master.002.patch, HBASE-19009.master.003.patch, 
> HBASE-19009.master.004.patch, HBASE-19009.master.005.patch, 
> HBASE-19009.master.006.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-18775) Add a Global Read-Only property to turn off all writes for the cluster

[Zach York (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241637#comment-16241637
 ] 

Zach York commented on HBASE-18775:
---

[~stack] Could you take a look when you get a chance?

[~ashish singhi] Are you okay with leaving snapshot operations for a separate 
JIRA?

> Add a Global Read-Only property to turn off all writes for the cluster
> --
>
> Key: HBASE-18775
> URL: https://issues.apache.org/jira/browse/HBASE-18775
> Project: HBase
>  Issue Type: Sub-task
>  Components: master, regionserver
>Affects Versions: HBASE-18477
>Reporter: Zach York
>Assignee: Zach York
> Attachments: HBASE-18775.HBASE-18477.001.patch, 
> HBASE-18775.HBASE-18477.002.patch, HBASE-18775.HBASE-18477.003.patch, 
> HBASE-18775.HBASE-18477.004.patch, HBASE-18775.HBASE-18477.005.patch, 
> HBASE-18775.HBASE-18477.006.patch, HBASE-18775.HBASE-18477.007.patch, 
> HBASE-18775.HBASE-18477.008.patch
>
>
> As part of HBASE-18477, we need a way to turn off all modification for a 
> cluster. This patch extends the read only mode used by replication to disable 
> all data and metadata operations.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-18775) Add a Global Read-Only property to turn off all writes for the cluster

[Zach York (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zach York updated HBASE-18775:
--
Attachment: HBASE-18775.HBASE-18477.008.patch

> Add a Global Read-Only property to turn off all writes for the cluster
> --
>
> Key: HBASE-18775
> URL: https://issues.apache.org/jira/browse/HBASE-18775
> Project: HBase
>  Issue Type: Sub-task
>  Components: master, regionserver
>Affects Versions: HBASE-18477
>Reporter: Zach York
>Assignee: Zach York
> Attachments: HBASE-18775.HBASE-18477.001.patch, 
> HBASE-18775.HBASE-18477.002.patch, HBASE-18775.HBASE-18477.003.patch, 
> HBASE-18775.HBASE-18477.004.patch, HBASE-18775.HBASE-18477.005.patch, 
> HBASE-18775.HBASE-18477.006.patch, HBASE-18775.HBASE-18477.007.patch, 
> HBASE-18775.HBASE-18477.008.patch
>
>
> As part of HBASE-18477, we need a way to turn off all modification for a 
> cluster. This patch extends the read only mode used by replication to disable 
> all data and metadata operations.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-18775) Add a Global Read-Only property to turn off all writes for the cluster

[Zach York (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zach York updated HBASE-18775:
--
Status: Patch Available  (was: In Progress)

> Add a Global Read-Only property to turn off all writes for the cluster
> --
>
> Key: HBASE-18775
> URL: https://issues.apache.org/jira/browse/HBASE-18775
> Project: HBase
>  Issue Type: Sub-task
>  Components: master, regionserver
>Affects Versions: HBASE-18477
>Reporter: Zach York
>Assignee: Zach York
> Attachments: HBASE-18775.HBASE-18477.001.patch, 
> HBASE-18775.HBASE-18477.002.patch, HBASE-18775.HBASE-18477.003.patch, 
> HBASE-18775.HBASE-18477.004.patch, HBASE-18775.HBASE-18477.005.patch, 
> HBASE-18775.HBASE-18477.006.patch, HBASE-18775.HBASE-18477.007.patch, 
> HBASE-18775.HBASE-18477.008.patch
>
>
> As part of HBASE-18477, we need a way to turn off all modification for a 
> cluster. This patch extends the read only mode used by replication to disable 
> all data and metadata operations.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-18775) Add a Global Read-Only property to turn off all writes for the cluster

[Zach York (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zach York updated HBASE-18775:
--
Status: In Progress  (was: Patch Available)

> Add a Global Read-Only property to turn off all writes for the cluster
> --
>
> Key: HBASE-18775
> URL: https://issues.apache.org/jira/browse/HBASE-18775
> Project: HBase
>  Issue Type: Sub-task
>  Components: master, regionserver
>Affects Versions: HBASE-18477
>Reporter: Zach York
>Assignee: Zach York
> Attachments: HBASE-18775.HBASE-18477.001.patch, 
> HBASE-18775.HBASE-18477.002.patch, HBASE-18775.HBASE-18477.003.patch, 
> HBASE-18775.HBASE-18477.004.patch, HBASE-18775.HBASE-18477.005.patch, 
> HBASE-18775.HBASE-18477.006.patch, HBASE-18775.HBASE-18477.007.patch, 
> HBASE-18775.HBASE-18477.008.patch
>
>
> As part of HBASE-18477, we need a way to turn off all modification for a 
> cluster. This patch extends the read only mode used by replication to disable 
> all data and metadata operations.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-12091) Optionally ignore edits for dropped tables for replication.

[Lars Hofhansl (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lars Hofhansl updated HBASE-12091:
--
Attachment: (was: 12091-v7-branch-1.txt)

> Optionally ignore edits for dropped tables for replication.
> ---
>
> Key: HBASE-12091
> URL: https://issues.apache.org/jira/browse/HBASE-12091
> Project: HBase
>  Issue Type: Bug
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
> Fix For: 1.4.0
>
> Attachments: 12091-branch-2.patch, 12091-v2-branch-1.txt, 
> 12091-v3-branch-1.txt, 12091-v4-branch-1.txt, 12091-v5-branch-1.txt, 
> 12091-v6-branch-1.txt, 12091-v7-branch-1.txt, 12091.txt
>
>
> We just ran into a scenario where we dropped a table from both the source and 
> the sink, but the source still has outstanding edits that now it could not 
> get rid of. Now all replication is backed up behind these unreplicatable 
> edits.
> We should have an option to ignore edits for tables dropped at the source.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-12091) Optionally ignore edits for dropped tables for replication.

[Lars Hofhansl (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lars Hofhansl updated HBASE-12091:
--
Attachment: 12091-v7-branch-1.txt

The right patch this time. Same contents.

> Optionally ignore edits for dropped tables for replication.
> ---
>
> Key: HBASE-12091
> URL: https://issues.apache.org/jira/browse/HBASE-12091
> Project: HBase
>  Issue Type: Bug
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
> Fix For: 1.4.0
>
> Attachments: 12091-branch-2.patch, 12091-v2-branch-1.txt, 
> 12091-v3-branch-1.txt, 12091-v4-branch-1.txt, 12091-v5-branch-1.txt, 
> 12091-v6-branch-1.txt, 12091-v7-branch-1.txt, 12091.txt
>
>
> We just ran into a scenario where we dropped a table from both the source and 
> the sink, but the source still has outstanding edits that now it could not 
> get rid of. Now all replication is backed up behind these unreplicatable 
> edits.
> We should have an option to ignore edits for tables dropped at the source.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19102) TestZooKeeperMainServer fails with KeeperException$ConnectionLossException

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241631#comment-16241631
 ] 

Hudson commented on HBASE-19102:


SUCCESS: Integrated in Jenkins build HBase-1.5 #140 (See 
[https://builds.apache.org/job/HBase-1.5/140/])
HBASE-19102 TestZooKeeperMainServer fails with KeeperException (stack: rev 
a2ae58f6eebe41a47bfb082d340323c4385f0620)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperMainServer.java


> TestZooKeeperMainServer fails with KeeperException$ConnectionLossException
> --
>
> Key: HBASE-19102
> URL: https://issues.apache.org/jira/browse/HBASE-19102
> Project: HBase
>  Issue Type: Bug
>Reporter: stack
>Assignee: stack
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1
>
> Attachments: HBASE-19102.master.001.patch, 
> HBASE-19102.master.002.patch, HBASE-19102.master.002.patch
>
>
> I'm trying to run test suite on a local machine. I never get to the second 
> part because I fail on below test with below exception near every time (and 
> an ipv6 test... will do that next).  
> 1 
> ---
>   2 Test set: org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   3 
> ---
>   4 Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 16.161 s 
> <<< FAILURE! - in org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   5 
> testCommandLineWorks(org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer)
>   Time elapsed: 15.848 s  <<< ERROR!
>   6 org.apache.zookeeper.KeeperException$ConnectionLossException: 
> KeeperErrorCode = ConnectionLoss for /testCommandLineWorks
>   7   at 
> org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer.testCommandLineWorks(TestZooKeeperMainServer.java:81)
> Looks like running the command before we are connected causes the above -- we 
> pause 15 seconds and then throw the above.   If I wait until connected before 
> proceding, stuff seems to work reliably. I don't have access to the watcher 
> on connections since we override the zk main class... so this seems only 
> avenue available at mo (This zk main thing is all a hack around zk main 
> because it had bugs ... but I think we have to keep the hack because folks 
> use different versions of zk. My $workplace defaults to something that is 
> years old, 3.4.5 for instance).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-12091) Optionally ignore edits for dropped tables for replication.

[Lars Hofhansl (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lars Hofhansl updated HBASE-12091:
--
Attachment: 12091-v7-branch-1.txt

OK...

-v7:
* streamline the tests
* make sure all tests clean up after themselves
* adds a test for the case where the source table is not deleted
* allow a replication endpoint to determine the local configuration (via the 
replication context)
* the sink will explicitly throw a table not found exception if one is 
encountered. The details are not important for the source.

This works. Passes all tests. And the tests cover all scenarios that I can 
think of.
This is more tricky than I thought. Please review carefully. Probably better to 
wait until 1.4.1 still.

(Going to bed now)

> Optionally ignore edits for dropped tables for replication.
> ---
>
> Key: HBASE-12091
> URL: https://issues.apache.org/jira/browse/HBASE-12091
> Project: HBase
>  Issue Type: Bug
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
> Fix For: 1.4.0
>
> Attachments: 12091-branch-2.patch, 12091-v2-branch-1.txt, 
> 12091-v3-branch-1.txt, 12091-v4-branch-1.txt, 12091-v5-branch-1.txt, 
> 12091-v6-branch-1.txt, 12091-v7-branch-1.txt, 12091.txt
>
>
> We just ran into a scenario where we dropped a table from both the source and 
> the sink, but the source still has outstanding edits that now it could not 
> get rid of. Now all replication is backed up behind these unreplicatable 
> edits.
> We should have an option to ignore edits for tables dropped at the source.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-19128) Purge Distributed Log Replay from codebase, configurations, text; mark the feature as unsupported, broken.

[Appy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Appy updated HBASE-19128:
-
Attachment: HBASE-19128.master.004.patch

> Purge Distributed Log Replay from codebase, configurations, text; mark the 
> feature as unsupported, broken.
> --
>
> Key: HBASE-19128
> URL: https://issues.apache.org/jira/browse/HBASE-19128
> Project: HBase
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: stack
>Assignee: Appy
>  Labels: incompatible
> Fix For: 2.0.0
>
> Attachments: HBASE-19128.master.001.patch, 
> HBASE-19128.master.002.patch, HBASE-19128.master.003.patch, 
> HBASE-19128.master.004.patch
>
>
> Kill it. It keeps coming up and over again. Needs proper burial.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-19174) Update link to HBase presentations

[Jan Hentschel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Hentschel updated HBASE-19174:
--
   Resolution: Fixed
Fix Version/s: 3.0.0
   Status: Resolved  (was: Patch Available)

Committed to master.

> Update link to HBase presentations
> --
>
> Key: HBASE-19174
> URL: https://issues.apache.org/jira/browse/HBASE-19174
> Project: HBase
>  Issue Type: Improvement
>  Components: documentation
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Trivial
> Fix For: 3.0.0
>
> Attachments: HBASE-19174.master.001.patch, 
> HBASE-19174.master.002.patch
>
>
> old_news.adoc references to the [Hadoop 
> wiki|https://wiki.apache.org/hadoop/HBase/HBasePresentations] for past 
> presentations. The page itself states that it will be decommissioned in the 
> future. The link should go to the book instead. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-19175) Add linklint files to gitignore

[Jan Hentschel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Hentschel updated HBASE-19175:
--
   Resolution: Fixed
Fix Version/s: 3.0.0
   Status: Resolved  (was: Patch Available)

Committed to master

> Add linklint files to gitignore
> ---
>
> Key: HBASE-19175
> URL: https://issues.apache.org/jira/browse/HBASE-19175
> Project: HBase
>  Issue Type: Improvement
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Trivial
> Fix For: 3.0.0
>
> Attachments: HBASE-19175.master.001.patch
>
>
> When running the check-website-links scripts locally instead of Jenkins 
> several files and directories are created. To prevent accidental addition to 
> the repository they should be added to the gitignore file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-19183) Removed redundant groupId from Maven modules

[Jan Hentschel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Hentschel updated HBASE-19183:
--
   Resolution: Fixed
Fix Version/s: 3.0.0
   Status: Resolved  (was: Patch Available)

Committed to master.

> Removed redundant groupId from Maven modules
> 
>
> Key: HBASE-19183
> URL: https://issues.apache.org/jira/browse/HBASE-19183
> Project: HBase
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Trivial
> Fix For: 3.0.0
>
> Attachments: HBASE-19183.master.001.patch
>
>
> Currently the modules hbase-checkstyle and hbase-error-prone define the 
> groupId redundantly. Remove the groupId from these POMs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-18624) Added support for clearing BlockCache based on table name

[Zach York (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-18624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zach York updated HBASE-18624:
--
Status: In Progress  (was: Patch Available)

> Added support for clearing BlockCache based on table name
> -
>
> Key: HBASE-18624
> URL: https://issues.apache.org/jira/browse/HBASE-18624
> Project: HBase
>  Issue Type: Sub-task
>Affects Versions: 1.3.0, 2.0.0
>Reporter: Ajay Jadhav
>Assignee: Zach York
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-18624.branch-1.001.patch, 
> HBASE-18624.master.001.patch, HBASE-18624.master.002.patch, 
> HBASE-18624.master.003.patch, HBASE-18624.master.004.patch, 
> HBASE-18624.master.005.patch, HBASE-18624.master.006.patch, 
> HBASE-18624.master.007.patch, HBASE-18624.master.008.patch, 
> HBASE-18624.master.009.patch, HBASE-18624.master.010.patch, 
> HBASE-18624.master.011.patch, HBASE-18624.master.012.patch, 
> HBASE-18624.master.013.patch
>
>
> Bulk loading the primary HBase cluster triggers a lot of compactions 
> resulting in archival/ creation
> of multiple HFiles. This process will cause a lot of items to become stale in 
> replica’s BlockCache.
> This patch will help users to clear the block cache for a given table by 
> either using shell or API.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-18624) Added support for clearing BlockCache based on table name

[Zach York (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-18624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zach York updated HBASE-18624:
--
Status: Patch Available  (was: In Progress)

> Added support for clearing BlockCache based on table name
> -
>
> Key: HBASE-18624
> URL: https://issues.apache.org/jira/browse/HBASE-18624
> Project: HBase
>  Issue Type: Sub-task
>Affects Versions: 1.3.0, 2.0.0
>Reporter: Ajay Jadhav
>Assignee: Zach York
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-18624.branch-1.001.patch, 
> HBASE-18624.master.001.patch, HBASE-18624.master.002.patch, 
> HBASE-18624.master.003.patch, HBASE-18624.master.004.patch, 
> HBASE-18624.master.005.patch, HBASE-18624.master.006.patch, 
> HBASE-18624.master.007.patch, HBASE-18624.master.008.patch, 
> HBASE-18624.master.009.patch, HBASE-18624.master.010.patch, 
> HBASE-18624.master.011.patch, HBASE-18624.master.012.patch, 
> HBASE-18624.master.013.patch
>
>
> Bulk loading the primary HBase cluster triggers a lot of compactions 
> resulting in archival/ creation
> of multiple HFiles. This process will cause a lot of items to become stale in 
> replica’s BlockCache.
> This patch will help users to clear the block cache for a given table by 
> either using shell or API.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-18624) Added support for clearing BlockCache based on table name

[Zach York (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-18624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zach York updated HBASE-18624:
--
Attachment: HBASE-18624.master.013.patch

> Added support for clearing BlockCache based on table name
> -
>
> Key: HBASE-18624
> URL: https://issues.apache.org/jira/browse/HBASE-18624
> Project: HBase
>  Issue Type: Sub-task
>Affects Versions: 2.0.0, 1.3.0
>Reporter: Ajay Jadhav
>Assignee: Zach York
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-18624.branch-1.001.patch, 
> HBASE-18624.master.001.patch, HBASE-18624.master.002.patch, 
> HBASE-18624.master.003.patch, HBASE-18624.master.004.patch, 
> HBASE-18624.master.005.patch, HBASE-18624.master.006.patch, 
> HBASE-18624.master.007.patch, HBASE-18624.master.008.patch, 
> HBASE-18624.master.009.patch, HBASE-18624.master.010.patch, 
> HBASE-18624.master.011.patch, HBASE-18624.master.012.patch, 
> HBASE-18624.master.013.patch
>
>
> Bulk loading the primary HBase cluster triggers a lot of compactions 
> resulting in archival/ creation
> of multiple HFiles. This process will cause a lot of items to become stale in 
> replica’s BlockCache.
> This patch will help users to clear the block cache for a given table by 
> either using shell or API.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-19103) Add BigDecimalComparator for filter

[Jan Hentschel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Hentschel updated HBASE-19103:
--
  Resolution: Fixed
Hadoop Flags: Reviewed
  Status: Resolved  (was: Patch Available)

Committed v3 to master. [~Qilin Cao] Thanks for the patch.

> Add BigDecimalComparator for filter
> ---
>
> Key: HBASE-19103
> URL: https://issues.apache.org/jira/browse/HBASE-19103
> Project: HBase
>  Issue Type: New Feature
>  Components: Client
>Reporter: Qilin Cao
>Assignee: Qilin Cao
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: HBASE-19103-1.2.0-v1.patch, HBASE-19103-1.2.0-v2.patch, 
> HBASE-19103-trunk-v1.patch, HBASE-19103-trunk-v2.patch, 
> HBASE-19103-trunk-v3.patch
>
>
> Should I add BigDecimalComparator for filter? Some scenarios need to 
> calculate the data accurately may use it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19009) implement enable/disableTableReplication for AsyncAdmin

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241602#comment-16241602
 ] 

Hadoop QA commented on HBASE-19009:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
10s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m  
0s{color} | {color:blue} Findbugs executables are not available. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green}  0m  
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green}  0m 
 0s{color} | {color:green} The patch appears to include 2 new or modified test 
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
33s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
53s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m  
3s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
35s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  6m 
28s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
57s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
15s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  5m 
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
15s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
35s{color} | {color:red} hbase-client: The patch generated 22 new + 251 
unchanged - 3 fixed = 273 total (was 254) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  1m 
12s{color} | {color:red} hbase-server: The patch generated 2 new + 3 unchanged 
- 2 fixed = 5 total (was 5) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  5m 
16s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
54m 43s{color} | {color:green} Patch does not cause any errors with Hadoop 
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
58s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  3m 
14s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 94m 18s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
33s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}176m 52s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-19009 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12896341/HBASE-19009.master.005.patch
 |
| Optional Tests |  asflicense  javac  javadoc  unit  findbugs  shadedjars  
hadoopcheck  hbaseanti  checkstyle  compile  |
| uname | Linux b339329f0e70 3.13.0-133-generic #182-Ubuntu SMP Tue Sep 19 
15:49:21 UTC 2017 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build@2/component/dev-support/hbase-personality.sh
 |
| 

[jira] [Comment Edited] (HBASE-12091) Optionally ignore edits for dropped tables for replication.

[Lars Hofhansl (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241542#comment-16241542
 ] 

Lars Hofhansl edited comment on HBASE-12091 at 11/7/17 7:04 AM:


Yeah. This is not ready, yet. The test is flawed still.
And with namespaces this throws a completely different exception message, from 
I cannot safely extract tablename.

And this
{code}
if (table != null && !conn.getAdmin().tableExists(table)) {
{code}
is the _wrong_ connection. It's the one for the peer - which obviously always 
won't have the table if it was dropped at the peer. I need to invent a way to 
get a connection to the local cluster.

Let's aim for 1.4.1.



was (Author: lhofhansl):
Yeah. This is not ready, yet. The test is flawed still.
And with namespaces this throws a completely different exception message, from 
I cannot safely extract tablename.

Let's aim for 1.4.1.

> Optionally ignore edits for dropped tables for replication.
> ---
>
> Key: HBASE-12091
> URL: https://issues.apache.org/jira/browse/HBASE-12091
> Project: HBase
>  Issue Type: Bug
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
> Fix For: 1.4.0
>
> Attachments: 12091-branch-2.patch, 12091-v2-branch-1.txt, 
> 12091-v3-branch-1.txt, 12091-v4-branch-1.txt, 12091-v5-branch-1.txt, 
> 12091-v6-branch-1.txt, 12091.txt
>
>
> We just ran into a scenario where we dropped a table from both the source and 
> the sink, but the source still has outstanding edits that now it could not 
> get rid of. Now all replication is backed up behind these unreplicatable 
> edits.
> We should have an option to ignore edits for tables dropped at the source.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (HBASE-12091) Optionally ignore edits for dropped tables for replication.

[Lars Hofhansl (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241542#comment-16241542
 ] 

Lars Hofhansl edited comment on HBASE-12091 at 11/7/17 6:41 AM:


Yeah. This is not ready, yet. The test is flawed still.
And with namespaces this throws a completely different exception message, from 
I cannot safely extract tablename.

Let's aim for 1.4.1.


was (Author: lhofhansl):
Yeah. This is not ready, yet. The test is flawed still. Let's aim for 1.4.1.

> Optionally ignore edits for dropped tables for replication.
> ---
>
> Key: HBASE-12091
> URL: https://issues.apache.org/jira/browse/HBASE-12091
> Project: HBase
>  Issue Type: Bug
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
> Fix For: 1.4.0
>
> Attachments: 12091-branch-2.patch, 12091-v2-branch-1.txt, 
> 12091-v3-branch-1.txt, 12091-v4-branch-1.txt, 12091-v5-branch-1.txt, 
> 12091-v6-branch-1.txt, 12091.txt
>
>
> We just ran into a scenario where we dropped a table from both the source and 
> the sink, but the source still has outstanding edits that now it could not 
> get rid of. Now all replication is backed up behind these unreplicatable 
> edits.
> We should have an option to ignore edits for tables dropped at the source.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (HBASE-12091) Optionally ignore edits for dropped tables for replication.

[Lars Hofhansl (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lars Hofhansl updated HBASE-12091:
--
Comment: was deleted

(was: The exception message with namespaces is different too.
Without namespace: "Table '' was not found".
With namespace: "Table : was not found". Notice the absence of the 
single quotes. W.T.F.?
)

> Optionally ignore edits for dropped tables for replication.
> ---
>
> Key: HBASE-12091
> URL: https://issues.apache.org/jira/browse/HBASE-12091
> Project: HBase
>  Issue Type: Bug
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
> Fix For: 1.4.0
>
> Attachments: 12091-branch-2.patch, 12091-v2-branch-1.txt, 
> 12091-v3-branch-1.txt, 12091-v4-branch-1.txt, 12091-v5-branch-1.txt, 
> 12091-v6-branch-1.txt, 12091.txt
>
>
> We just ran into a scenario where we dropped a table from both the source and 
> the sink, but the source still has outstanding edits that now it could not 
> get rid of. Now all replication is backed up behind these unreplicatable 
> edits.
> We should have an option to ignore edits for tables dropped at the source.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19177) Determine if custom maven-fluido-skin jar is still necessary

[Peter Somogyi (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241579#comment-16241579
 ] 

Peter Somogyi commented on HBASE-19177:
---

That's already a big progress because using the old fluido-skin the site 
generation failed.

> Determine if custom maven-fluido-skin jar is still necessary
> 
>
> Key: HBASE-19177
> URL: https://issues.apache.org/jira/browse/HBASE-19177
> Project: HBase
>  Issue Type: Task
>  Components: site
>Reporter: Josh Elser
>Assignee: Josh Elser
> Fix For: 2.0.0-beta-1
>
>
> To get a fancy, mobile-friendly website, HBASE-14785 introduced a patched 
> version of the maven-fluido-skin and committed the pre-built jar into our 
> release.
> A few folks have noticed this jar lurking around the 2.0.0 alpha releases. By 
> version number, it doesn't seem like we'd need to have this anymore (and can 
> use the newest version).
> Let's check it out.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-12091) Optionally ignore edits for dropped tables for replication.

[Lars Hofhansl (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241576#comment-16241576
 ] 

Lars Hofhansl commented on HBASE-12091:
---

The exception message with namespaces is different too.
Without namespace: "Table '' was not found".
With namespace: "Table : was not found". Notice the absence of the 
single quotes. W.T.F.?


> Optionally ignore edits for dropped tables for replication.
> ---
>
> Key: HBASE-12091
> URL: https://issues.apache.org/jira/browse/HBASE-12091
> Project: HBase
>  Issue Type: Bug
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
> Fix For: 1.4.0
>
> Attachments: 12091-branch-2.patch, 12091-v2-branch-1.txt, 
> 12091-v3-branch-1.txt, 12091-v4-branch-1.txt, 12091-v5-branch-1.txt, 
> 12091-v6-branch-1.txt, 12091.txt
>
>
> We just ran into a scenario where we dropped a table from both the source and 
> the sink, but the source still has outstanding edits that now it could not 
> get rid of. Now all replication is backed up behind these unreplicatable 
> edits.
> We should have an option to ignore edits for tables dropped at the source.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19195) More error-prone fixes

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241573#comment-16241573
 ] 

Hadoop QA commented on HBASE-19195:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
9s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m  
0s{color} | {color:blue} Findbugs executables are not available. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green}  0m  
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green}  0m 
 0s{color} | {color:green} The patch appears to include 6 new or modified test 
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
22s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
20s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
18s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
40s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  6m 
 4s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
58s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
11s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
20s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
20s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
20s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
26s{color} | {color:red} hbase-client: The patch generated 2 new + 56 unchanged 
- 0 fixed = 58 total (was 56) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
16s{color} | {color:red} hbase-mapreduce: The patch generated 2 new + 78 
unchanged - 2 fixed = 80 total (was 80) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  4m 
24s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
44m 25s{color} | {color:green} Patch does not cause any errors with Hadoop 
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
58s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  2m 
38s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 98m 18s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 13m 
45s{color} | {color:green} hbase-mapreduce in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
50s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}182m  7s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.util.TestFromClientSide3WoUnsafe |
|   | hadoop.hbase.client.TestFromClientSide3 |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-19195 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12896334/HBASE-19195.patch |
| Optional Tests |  asflicense  javac  javadoc  unit  findbugs  shadedjars  
hadoopcheck  hbaseanti  

[jira] [Commented] (HBASE-19197) Move version on branch-2 from 2.0.0-alpha4 to 2.0.0-beta-1.SNAPSHOT

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241570#comment-16241570
 ] 

Hudson commented on HBASE-19197:


FAILURE: Integrated in Jenkins build HBase-2.0 #811 (See 
[https://builds.apache.org/job/HBase-2.0/811/])
HBASE-19197 Move version on branch-2 from 2.0.0-alpha4 to (stack: rev 
f13cf56f1c45cd172163ebe919a81536a843364c)
* (edit) hbase-archetypes/hbase-client-project/pom.xml
* (edit) hbase-thrift/pom.xml
* (edit) hbase-archetypes/hbase-shaded-client-project/pom.xml
* (edit) hbase-server/pom.xml
* (edit) hbase-shaded/hbase-shaded-check-invariants/pom.xml
* (edit) hbase-backup/pom.xml
* (edit) hbase-hadoop2-compat/pom.xml
* (edit) hbase-http/pom.xml
* (edit) hbase-rsgroup/pom.xml
* (edit) hbase-protocol-shaded/pom.xml
* (edit) hbase-it/pom.xml
* (edit) hbase-shaded/hbase-shaded-mapreduce/pom.xml
* (edit) hbase-shaded/pom.xml
* (edit) hbase-assembly/pom.xml
* (edit) hbase-common/pom.xml
* (edit) hbase-hadoop-compat/pom.xml
* (edit) hbase-shaded/hbase-shaded-client/pom.xml
* (edit) hbase-external-blockcache/pom.xml
* (edit) hbase-procedure/pom.xml
* (edit) hbase-protocol/pom.xml
* (edit) hbase-shell/pom.xml
* (edit) hbase-metrics/pom.xml
* (edit) hbase-endpoint/pom.xml
* (edit) hbase-client/pom.xml
* (edit) hbase-annotations/pom.xml
* (edit) hbase-archetypes/pom.xml
* (edit) hbase-spark-it/pom.xml
* (edit) hbase-spark/pom.xml
* (edit) hbase-checkstyle/pom.xml
* (edit) hbase-examples/pom.xml
* (edit) hbase-metrics-api/pom.xml
* (edit) hbase-rest/pom.xml
* (edit) pom.xml
* (edit) hbase-resource-bundle/pom.xml
* (edit) hbase-testing-util/pom.xml
* (edit) hbase-archetypes/hbase-archetype-builder/pom.xml
* (edit) hbase-build-configuration/pom.xml
* (edit) hbase-mapreduce/pom.xml
* (edit) hbase-replication/pom.xml


> Move version on branch-2 from 2.0.0-alpha4 to 2.0.0-beta-1.SNAPSHOT
> ---
>
> Key: HBASE-19197
> URL: https://issues.apache.org/jira/browse/HBASE-19197
> Project: HBase
>  Issue Type: Sub-task
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0-beta-1
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19198) TestIPv6NIOServerSocketChannel fails; unable to bind

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241571#comment-16241571
 ] 

Hudson commented on HBASE-19198:


FAILURE: Integrated in Jenkins build HBase-2.0 #811 (See 
[https://builds.apache.org/job/HBase-2.0/811/])
HBASE-19198 TestIPv6NIOServerSocketChannel fails; unable to bind (stack: rev 
57c0fb2561b63384d38072ba0bf16f7182a3a5cc)
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/TestIPv6NIOServerSocketChannel.java


> TestIPv6NIOServerSocketChannel fails; unable to bind
> 
>
> Key: HBASE-19198
> URL: https://issues.apache.org/jira/browse/HBASE-19198
> Project: HBase
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.0.0-beta-1
>Reporter: stack
>Assignee: stack
>Priority: Minor
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1
>
>
> This test always fails on some hardware I have here abouts.
> The test is sort of odd in that it asks to resolve 'localhost'. In my case, I 
> get back two addresses: 127.0.0.1 and then a nonsense one, 205.127.0.0 which 
> looks like a managled address.
> I've tried to figure how resolve is broke on this machine but configs look 
> good and dig/host using 'localhost' fails because it ain't an address to 
> resolve.
> Given latter, I'm changing the test to use getLocalHost which is what it is 
> trying to look up



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19186) Unify to use bytes to show size in master/rs ui

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241569#comment-16241569
 ] 

Hudson commented on HBASE-19186:


FAILURE: Integrated in Jenkins build HBase-2.0 #811 (See 
[https://builds.apache.org/job/HBase-2.0/811/])
HBASE-19186 Unify to use bytes to show size in master/rs ui (zghao: rev 
40dac699bd7ca37fd2401d60f10bebb8a856ad88)
* (delete) hbase-server/src/main/resources/hbase-webapps/master/processRS.jsp
* (edit) hbase-server/src/main/resources/hbase-webapps/master/processMaster.jsp
* (edit) 
hbase-server/src/main/resources/hbase-webapps/regionserver/processRS.jsp
* (edit) hbase-server/src/main/resources/hbase-webapps/master/procedures.jsp
* (edit) 
hbase-server/src/main/jamon/org/apache/hadoop/hbase/tmpl/regionserver/BlockCacheTmpl.jamon
* (edit) hbase-server/src/main/resources/hbase-webapps/master/table.jsp
* (edit) 
hbase-server/src/main/jamon/org/apache/hadoop/hbase/tmpl/regionserver/ServerMetricsTmpl.jamon


> Unify to use bytes to show size in master/rs ui
> ---
>
> Key: HBASE-19186
> URL: https://issues.apache.org/jira/browse/HBASE-19186
> Project: HBase
>  Issue Type: Improvement
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Minor
> Fix For: 3.0.0, 2.0.0-beta-1
>
> Attachments: HBASE-19186.master.001.patch, master-process.png, 
> procedure-wal-state.png, procedure-wal-sync-stats.png, 
> regions-storefiles.png, regionserver-blockcache.png, regionserver-memory.png, 
> regionserver-process.png, regionserver-storefiles.png, 
> server-metrics-memory.png, server-metrics-storefiles.png
>
>
> 1. 10K ==> 10KB or 10M ==> 10MB or 10G => 10GB
> 2. remove "in bytes" in description



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19127) Set State.SPLITTING, MERGING, MERGING_NEW, SPLITTING_NEW properly in RegionStatesNode

[stack (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241543#comment-16241543
 ] 

stack commented on HBASE-19127:
---

Thank you for looking at this [~easyliangjob]

Don't change numbering in protobufs.

What does the change in AM do? (Adding state for daughters)?

Otherwise patch looks great.

Failures related?

Thanks.

> Set State.SPLITTING, MERGING, MERGING_NEW, SPLITTING_NEW properly in 
> RegionStatesNode
> -
>
> Key: HBASE-19127
> URL: https://issues.apache.org/jira/browse/HBASE-19127
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Yi Liang
>Assignee: Yi Liang
> Attachments: state.patch
>
>
> In current code, we did not set above states to a region node at all, but we 
> still have statements like below to check if node have above states.
> {code}
> else if (!regionNode.isInState(State.CLOSING, State.SPLITTING)) {
> 
> }
> {code}
> We need to set above states in a correct place.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-12091) Optionally ignore edits for dropped tables for replication.

[Lars Hofhansl (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241542#comment-16241542
 ] 

Lars Hofhansl commented on HBASE-12091:
---

Yeah. This is not ready, yet. The test is flawed still. Let's aim for 1.4.1.

> Optionally ignore edits for dropped tables for replication.
> ---
>
> Key: HBASE-12091
> URL: https://issues.apache.org/jira/browse/HBASE-12091
> Project: HBase
>  Issue Type: Bug
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
> Fix For: 1.4.0
>
> Attachments: 12091-branch-2.patch, 12091-v2-branch-1.txt, 
> 12091-v3-branch-1.txt, 12091-v4-branch-1.txt, 12091-v5-branch-1.txt, 
> 12091-v6-branch-1.txt, 12091.txt
>
>
> We just ran into a scenario where we dropped a table from both the source and 
> the sink, but the source still has outstanding edits that now it could not 
> get rid of. Now all replication is backed up behind these unreplicatable 
> edits.
> We should have an option to ignore edits for tables dropped at the source.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19095) Add CP hooks in RegionObserver for in memory compaction

[stack (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241536#comment-16241536
 ] 

stack commented on HBASE-19095:
---

bq. Or it was killed by someone?

Yeah. Probably the OS. You saw the deadly battle going on over in HDFS-12711 
trying to contain hadoop burning down the build boxes? That should be 'fixed' 
now. Maybe something else. Sean added nice stuff to yetus so can see what 
environment is like... Will report back.

> Add CP hooks in RegionObserver for in memory compaction
> ---
>
> Key: HBASE-19095
> URL: https://issues.apache.org/jira/browse/HBASE-19095
> Project: HBase
>  Issue Type: Sub-task
>  Components: Coprocessors
>Reporter: Duo Zhang
>Assignee: Duo Zhang
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19095-v1.patch, HBASE-19095-v2.patch, 
> HBASE-19095-v3.patch, HBASE-19095.patch
>
>
> This is a hole in our CP hooks.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (HBASE-19165) TODO Handle stuck in transition: rit=OPENING, location=ve0538....

[stack (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241250#comment-16241250
 ] 

stack edited comment on HBASE-19165 at 11/7/17 5:49 AM:


Test failure is a good one. I filed HBASE-19193 to address it later. The test 
failure is part of a larger issue of what to do when empty state (Can have 
empty state as part of migration but HBASE-19193 shows we can have an empty 
state if Master crashes in midst of a Table delete..Good one).


was (Author: stack):
Test failure is a good one. I filed HBASE-19165 to address it later. The test 
failure is part of a larger issue of what to do when empty state (Can have 
empty state as part of migration but HBASE-19193 shows we can have an empty 
state if Master crashes in midst of a Table delete..Good one).

> TODO Handle stuck in transition: rit=OPENING, location=ve0538
> -
>
> Key: HBASE-19165
> URL: https://issues.apache.org/jira/browse/HBASE-19165
> Project: HBase
>  Issue Type: Bug
>  Components: migration
>Reporter: stack
>Assignee: stack
>Priority: Critical
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19165.master.001.patch, 
> HBASE-19165.master.002.patch
>
>
> A few of us trying migration from hbase1 to hbase2 have run into various 
> assignment issues. In my case, I see that Master coming online, reading 
> hbase:meta, finding an issue in OPENING state and then just not assigning. My 
> thought is that its expecting a callback to come in. Eventually log is fills 
> with this sort of stuff:
> 2017-11-02 15:02:54,237 WARN  [ProcExecTimeout] assignment.AssignmentManager: 
> TODO Handle stuck in transition: rit=OPENING, 
> location=ve0528.halxg.cloudera.com,16020,1509657692581, 
> table=IntegrationTestBigLinkedList, region=919cc6636ffbed17f628f335d3a58726
> Let me get a cleaner run. This current log is polluted by a few restarts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19198) TestIPv6NIOServerSocketChannel fails; unable to bind

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241524#comment-16241524
 ] 

Hudson commented on HBASE-19198:


SUCCESS: Integrated in Jenkins build HBase-1.2-IT #1008 (See 
[https://builds.apache.org/job/HBase-1.2-IT/1008/])
HBASE-19198 TestIPv6NIOServerSocketChannel fails; unable to bind (stack: rev 
2735883361e488a57f70ac5d65073528a5b474bb)
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/TestIPv6NIOServerSocketChannel.java


> TestIPv6NIOServerSocketChannel fails; unable to bind
> 
>
> Key: HBASE-19198
> URL: https://issues.apache.org/jira/browse/HBASE-19198
> Project: HBase
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.0.0-beta-1
>Reporter: stack
>Assignee: stack
>Priority: Minor
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1
>
>
> This test always fails on some hardware I have here abouts.
> The test is sort of odd in that it asks to resolve 'localhost'. In my case, I 
> get back two addresses: 127.0.0.1 and then a nonsense one, 205.127.0.0 which 
> looks like a managled address.
> I've tried to figure how resolve is broke on this machine but configs look 
> good and dig/host using 'localhost' fails because it ain't an address to 
> resolve.
> Given latter, I'm changing the test to use getLocalHost which is what it is 
> trying to look up



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19198) TestIPv6NIOServerSocketChannel fails; unable to bind

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241520#comment-16241520
 ] 

Hudson commented on HBASE-19198:


SUCCESS: Integrated in Jenkins build HBase-1.3-IT #275 (See 
[https://builds.apache.org/job/HBase-1.3-IT/275/])
HBASE-19198 TestIPv6NIOServerSocketChannel fails; unable to bind (stack: rev 
342328bdd841596c426feac569f20024e95a6a4b)
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/TestIPv6NIOServerSocketChannel.java


> TestIPv6NIOServerSocketChannel fails; unable to bind
> 
>
> Key: HBASE-19198
> URL: https://issues.apache.org/jira/browse/HBASE-19198
> Project: HBase
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.0.0-beta-1
>Reporter: stack
>Assignee: stack
>Priority: Minor
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1
>
>
> This test always fails on some hardware I have here abouts.
> The test is sort of odd in that it asks to resolve 'localhost'. In my case, I 
> get back two addresses: 127.0.0.1 and then a nonsense one, 205.127.0.0 which 
> looks like a managled address.
> I've tried to figure how resolve is broke on this machine but configs look 
> good and dig/host using 'localhost' fails because it ain't an address to 
> resolve.
> Given latter, I'm changing the test to use getLocalHost which is what it is 
> trying to look up



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (HBASE-12091) Optionally ignore edits for dropped tables for replication.

[Lars Hofhansl (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241507#comment-16241507
 ] 

Lars Hofhansl edited comment on HBASE-12091 at 11/7/17 5:38 AM:


OK... Lemme fix the comments. And actually I want to add one more important 
test: The remote table is gone, but the local table still exists. That should 
block replication.

Also no concern if this goes in for 1.4.1.


was (Author: lhofhansl):
OK... Lemme fix the comments. And actually I want to add one more important 
test: The remote table is gone, but the local table still exists. That should 
block replication.

> Optionally ignore edits for dropped tables for replication.
> ---
>
> Key: HBASE-12091
> URL: https://issues.apache.org/jira/browse/HBASE-12091
> Project: HBase
>  Issue Type: Bug
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
> Fix For: 1.4.0
>
> Attachments: 12091-branch-2.patch, 12091-v2-branch-1.txt, 
> 12091-v3-branch-1.txt, 12091-v4-branch-1.txt, 12091-v5-branch-1.txt, 
> 12091-v6-branch-1.txt, 12091.txt
>
>
> We just ran into a scenario where we dropped a table from both the source and 
> the sink, but the source still has outstanding edits that now it could not 
> get rid of. Now all replication is backed up behind these unreplicatable 
> edits.
> We should have an option to ignore edits for tables dropped at the source.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-12091) Optionally ignore edits for dropped tables for replication.

[Lars Hofhansl (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241507#comment-16241507
 ] 

Lars Hofhansl commented on HBASE-12091:
---

OK... Lemme fix the comments. And actually I want to add one more important 
test: The remote table is gone, but the local table still exists. That should 
block replication.

> Optionally ignore edits for dropped tables for replication.
> ---
>
> Key: HBASE-12091
> URL: https://issues.apache.org/jira/browse/HBASE-12091
> Project: HBase
>  Issue Type: Bug
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
> Fix For: 1.4.0
>
> Attachments: 12091-branch-2.patch, 12091-v2-branch-1.txt, 
> 12091-v3-branch-1.txt, 12091-v4-branch-1.txt, 12091-v5-branch-1.txt, 
> 12091-v6-branch-1.txt, 12091.txt
>
>
> We just ran into a scenario where we dropped a table from both the source and 
> the sink, but the source still has outstanding edits that now it could not 
> get rid of. Now all replication is backed up behind these unreplicatable 
> edits.
> We should have an option to ignore edits for tables dropped at the source.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19075) Task tabs on master UI cause page scroll

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241509#comment-16241509
 ] 

Hadoop QA commented on HBASE-19075:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
38s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red}  0m  
0s{color} | {color:red} The patch doesn't appear to include any new or modified 
tests. Please justify why no new tests are needed for this patch. Also please 
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
48s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
29s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
26s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
27s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 95m 
49s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
17s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}107m  5s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-19075 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12896054/HBASE-19075.master.001.patch
 |
| Optional Tests |  asflicense  javac  javadoc  unit  |
| uname | Linux 3589a014480a 3.13.0-133-generic #182-Ubuntu SMP Tue Sep 19 
15:49:21 UTC 2017 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
 |
| git revision | master / b6011a16ff |
| maven | version: Apache Maven 3.5.2 
(138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z) |
| Default Java | 1.8.0_151 |
|  Test Results | 
https://builds.apache.org/job/PreCommit-HBASE-Build/9648/testReport/ |
| modules | C: hbase-server U: hbase-server |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/9648/console |
| Powered by | Apache Yetus 0.6.0   http://yetus.apache.org |


This message was automatically generated.



> Task tabs on master UI cause page scroll
> 
>
> Key: HBASE-19075
> URL: https://issues.apache.org/jira/browse/HBASE-19075
> Project: HBase
>  Issue Type: Bug
>  Components: master
>Reporter: Mike Drob
>Assignee: Sahil Aggarwal
>  Labels: beginner
> Fix For: 2.0.0
>
> Attachments: HBASE-19075.master.001.patch
>
>
> On the master info page, the clicking the tabs under Tasks causes the page to 
> scroll back to the top of the page.
> {noformat}
> Tasks
> Show All Monitored Tasks Show non-RPC Tasks Show All RPC Handler Tasks Show 
> Active RPC Calls Show Client Operations View as JSON
> {noformat}
> ^^ Any of those
> The other tab-like links on the page keep the scroll in the same location.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19198) TestIPv6NIOServerSocketChannel fails; unable to bind

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241505#comment-16241505
 ] 

Hudson commented on HBASE-19198:


FAILURE: Integrated in Jenkins build HBase-1.2-JDK7 #269 (See 
[https://builds.apache.org/job/HBase-1.2-JDK7/269/])
HBASE-19198 TestIPv6NIOServerSocketChannel fails; unable to bind (stack: rev 
2735883361e488a57f70ac5d65073528a5b474bb)
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/TestIPv6NIOServerSocketChannel.java


> TestIPv6NIOServerSocketChannel fails; unable to bind
> 
>
> Key: HBASE-19198
> URL: https://issues.apache.org/jira/browse/HBASE-19198
> Project: HBase
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.0.0-beta-1
>Reporter: stack
>Assignee: stack
>Priority: Minor
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1
>
>
> This test always fails on some hardware I have here abouts.
> The test is sort of odd in that it asks to resolve 'localhost'. In my case, I 
> get back two addresses: 127.0.0.1 and then a nonsense one, 205.127.0.0 which 
> looks like a managled address.
> I've tried to figure how resolve is broke on this machine but configs look 
> good and dig/host using 'localhost' fails because it ain't an address to 
> resolve.
> Given latter, I'm changing the test to use getLocalHost which is what it is 
> trying to look up



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19198) TestIPv6NIOServerSocketChannel fails; unable to bind

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241504#comment-16241504
 ] 

Hudson commented on HBASE-19198:


FAILURE: Integrated in Jenkins build HBase-1.2-JDK8 #266 (See 
[https://builds.apache.org/job/HBase-1.2-JDK8/266/])
HBASE-19198 TestIPv6NIOServerSocketChannel fails; unable to bind (stack: rev 
2735883361e488a57f70ac5d65073528a5b474bb)
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/TestIPv6NIOServerSocketChannel.java


> TestIPv6NIOServerSocketChannel fails; unable to bind
> 
>
> Key: HBASE-19198
> URL: https://issues.apache.org/jira/browse/HBASE-19198
> Project: HBase
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.0.0-beta-1
>Reporter: stack
>Assignee: stack
>Priority: Minor
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1
>
>
> This test always fails on some hardware I have here abouts.
> The test is sort of odd in that it asks to resolve 'localhost'. In my case, I 
> get back two addresses: 127.0.0.1 and then a nonsense one, 205.127.0.0 which 
> looks like a managled address.
> I've tried to figure how resolve is broke on this machine but configs look 
> good and dig/host using 'localhost' fails because it ain't an address to 
> resolve.
> Given latter, I'm changing the test to use getLocalHost which is what it is 
> trying to look up



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19198) TestIPv6NIOServerSocketChannel fails; unable to bind

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241501#comment-16241501
 ] 

Hudson commented on HBASE-19198:


FAILURE: Integrated in Jenkins build HBase-1.3-JDK7 #337 (See 
[https://builds.apache.org/job/HBase-1.3-JDK7/337/])
HBASE-19198 TestIPv6NIOServerSocketChannel fails; unable to bind (stack: rev 
342328bdd841596c426feac569f20024e95a6a4b)
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/TestIPv6NIOServerSocketChannel.java


> TestIPv6NIOServerSocketChannel fails; unable to bind
> 
>
> Key: HBASE-19198
> URL: https://issues.apache.org/jira/browse/HBASE-19198
> Project: HBase
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.0.0-beta-1
>Reporter: stack
>Assignee: stack
>Priority: Minor
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1
>
>
> This test always fails on some hardware I have here abouts.
> The test is sort of odd in that it asks to resolve 'localhost'. In my case, I 
> get back two addresses: 127.0.0.1 and then a nonsense one, 205.127.0.0 which 
> looks like a managled address.
> I've tried to figure how resolve is broke on this machine but configs look 
> good and dig/host using 'localhost' fails because it ain't an address to 
> resolve.
> Given latter, I'm changing the test to use getLocalHost which is what it is 
> trying to look up



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (HBASE-17375) PrefixTreeArrayReversibleScanner#previousRowInternal doesn't work correctly

[stack (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-17375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack resolved HBASE-17375.
---
Resolution: Won't Fix

[~baibaichen] doesn't use this any more. We've removed this in branch-2 so 
resolving as won't fix.

> PrefixTreeArrayReversibleScanner#previousRowInternal doesn't work correctly
> ---
>
> Key: HBASE-17375
> URL: https://issues.apache.org/jira/browse/HBASE-17375
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 1.1.7, 0.98.23, 0.98.24
>Reporter: Chang chen
>Assignee: Chang chen
> Fix For: 2.0.0
>
> Attachments: HBASE_17375_master_v1.patch, row trie example.PNG
>
>
> Recently, we find our hbase compaction thread never end.  Assume we have 
> following cells:
> {quote}
>  1
>  1
>  1
>  1
>  1
>  1
>  1
>  1
> {quote}
> If we encode above datas into prefix tree block, then it looks like:
> !row trie example.PNG!
> Assume the current row is {color:red}Abc{color} (e.g. the current row node is 
> 4), then the previous row should be *Aa* (e.g. 2). However 
> previousRowInternal return {color:red}A{color}(e.g. 1)
> After investigation, I believe it's the bug of 
> PrefixTreeArrayReversibleScanner#previousRowInternal.
> {code}
>   private boolean previousRowInternal() {
> //...
> while (!beforeFirst) {
>   //
>   // what if currentRowNode is nub?
>   if (currentRowNode.hasOccurrences()) {// escape clause
> currentRowNode.resetFanIndex();
> return true;// found some values
>   }
> }
> {code}
> currentRowNode.hasOccurrences() only test whether it has cell or not. But in 
> the case of  currentRowNode.isNub() is true, previousRowInternal should 
> follow the previous fan instead of return.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-17375) PrefixTreeArrayReversibleScanner#previousRowInternal doesn't work correctly

[stack (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-17375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241498#comment-16241498
 ] 

stack commented on HBASE-17375:
---

Thank you [~baibaichen]

> PrefixTreeArrayReversibleScanner#previousRowInternal doesn't work correctly
> ---
>
> Key: HBASE-17375
> URL: https://issues.apache.org/jira/browse/HBASE-17375
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 1.1.7, 0.98.23, 0.98.24
>Reporter: Chang chen
>Assignee: Chang chen
> Fix For: 2.0.0
>
> Attachments: HBASE_17375_master_v1.patch, row trie example.PNG
>
>
> Recently, we find our hbase compaction thread never end.  Assume we have 
> following cells:
> {quote}
>  1
>  1
>  1
>  1
>  1
>  1
>  1
>  1
> {quote}
> If we encode above datas into prefix tree block, then it looks like:
> !row trie example.PNG!
> Assume the current row is {color:red}Abc{color} (e.g. the current row node is 
> 4), then the previous row should be *Aa* (e.g. 2). However 
> previousRowInternal return {color:red}A{color}(e.g. 1)
> After investigation, I believe it's the bug of 
> PrefixTreeArrayReversibleScanner#previousRowInternal.
> {code}
>   private boolean previousRowInternal() {
> //...
> while (!beforeFirst) {
>   //
>   // what if currentRowNode is nub?
>   if (currentRowNode.hasOccurrences()) {// escape clause
> currentRowNode.resetFanIndex();
> return true;// found some values
>   }
> }
> {code}
> currentRowNode.hasOccurrences() only test whether it has cell or not. But in 
> the case of  currentRowNode.isNub() is true, previousRowInternal should 
> follow the previous fan instead of return.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (HBASE-19198) TestIPv6NIOServerSocketChannel fails; unable to bind

[stack (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack resolved HBASE-19198.
---
   Resolution: Fixed
Fix Version/s: 2.0.0-beta-1
   1.2.7
   1.3.2
   1.4.0

Pushed below to 1.2+

commit d4e973d2dea272e8e156adec52a537ac5de3ff4e
Author: Michael Stack 
Date:   Mon Nov 6 21:19:51 2017 -0800

HBASE-19198 TestIPv6NIOServerSocketChannel fails; unable to bind

diff --git 
a/hbase-server/src/test/java/org/apache/hadoop/hbase/TestIPv6NIOServerSocketChannel.java
 
b/hbase-server/src/test/java/org/apache/hadoop/hbase/TestIPv6NIOServerSocketChannel.java
index 6b0b538..3dc2871 100644
--- 
a/hbase-server/src/test/java/org/apache/hadoop/hbase/TestIPv6NIOServerSocketChannel.java
+++ 
b/hbase-server/src/test/java/org/apache/hadoop/hbase/TestIPv6NIOServerSocketChannel.java
@@ -48,7 +48,6 @@ import org.junit.rules.TestRule;
  */
 @Category(SmallTests.class)
 public class TestIPv6NIOServerSocketChannel {
-
   private static final Log LOG = 
LogFactory.getLog(TestIPv6NIOServerSocketChannel.class);

   @Rule
@@ -68,6 +67,7 @@ public class TestIPv6NIOServerSocketChannel {
 break;
   } catch (BindException ex) {
 //continue
+LOG.info("Failed on " + addr + ", inedAddr=" + inetAddr, ex);
   } finally {
 if (serverSocket != null) {
   serverSocket.close();
@@ -150,9 +150,9 @@ public class TestIPv6NIOServerSocketChannel {
*/
   @Test
   public void testServerSocketFromLocalhostResolution() throws IOException {
-InetAddress[] addrs = InetAddress.getAllByName("localhost");
+InetAddress[] addrs = {InetAddress.getLocalHost()};
 for (InetAddress addr : addrs) {
-  LOG.info("resolved localhost as:" + addr);
+  LOG.info("Resolved localhost as: " + addr);
   bindServerSocket(addr);
   bindNIOServerSocket(addr);
 }

> TestIPv6NIOServerSocketChannel fails; unable to bind
> 
>
> Key: HBASE-19198
> URL: https://issues.apache.org/jira/browse/HBASE-19198
> Project: HBase
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.0.0-beta-1
>Reporter: stack
>Assignee: stack
>Priority: Minor
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1
>
>
> This test always fails on some hardware I have here abouts.
> The test is sort of odd in that it asks to resolve 'localhost'. In my case, I 
> get back two addresses: 127.0.0.1 and then a nonsense one, 205.127.0.0 which 
> looks like a managled address.
> I've tried to figure how resolve is broke on this machine but configs look 
> good and dig/host using 'localhost' fails because it ain't an address to 
> resolve.
> Given latter, I'm changing the test to use getLocalHost which is what it is 
> trying to look up



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19198) TestIPv6NIOServerSocketChannel fails; unable to bind

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241495#comment-16241495
 ] 

Hudson commented on HBASE-19198:


FAILURE: Integrated in Jenkins build HBase-1.3-JDK8 #356 (See 
[https://builds.apache.org/job/HBase-1.3-JDK8/356/])
HBASE-19198 TestIPv6NIOServerSocketChannel fails; unable to bind (stack: rev 
342328bdd841596c426feac569f20024e95a6a4b)
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/TestIPv6NIOServerSocketChannel.java


> TestIPv6NIOServerSocketChannel fails; unable to bind
> 
>
> Key: HBASE-19198
> URL: https://issues.apache.org/jira/browse/HBASE-19198
> Project: HBase
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.0.0-beta-1
>Reporter: stack
>Assignee: stack
>Priority: Minor
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1
>
>
> This test always fails on some hardware I have here abouts.
> The test is sort of odd in that it asks to resolve 'localhost'. In my case, I 
> get back two addresses: 127.0.0.1 and then a nonsense one, 205.127.0.0 which 
> looks like a managled address.
> I've tried to figure how resolve is broke on this machine but configs look 
> good and dig/host using 'localhost' fails because it ain't an address to 
> resolve.
> Given latter, I'm changing the test to use getLocalHost which is what it is 
> trying to look up



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-17375) PrefixTreeArrayReversibleScanner#previousRowInternal doesn't work correctly

[Chang chen (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-17375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241497#comment-16241497
 ] 

Chang chen commented on HBASE-17375:


yes please, we already replaced it.

> PrefixTreeArrayReversibleScanner#previousRowInternal doesn't work correctly
> ---
>
> Key: HBASE-17375
> URL: https://issues.apache.org/jira/browse/HBASE-17375
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 1.1.7, 0.98.23, 0.98.24
>Reporter: Chang chen
>Assignee: Chang chen
> Fix For: 2.0.0
>
> Attachments: HBASE_17375_master_v1.patch, row trie example.PNG
>
>
> Recently, we find our hbase compaction thread never end.  Assume we have 
> following cells:
> {quote}
>  1
>  1
>  1
>  1
>  1
>  1
>  1
>  1
> {quote}
> If we encode above datas into prefix tree block, then it looks like:
> !row trie example.PNG!
> Assume the current row is {color:red}Abc{color} (e.g. the current row node is 
> 4), then the previous row should be *Aa* (e.g. 2). However 
> previousRowInternal return {color:red}A{color}(e.g. 1)
> After investigation, I believe it's the bug of 
> PrefixTreeArrayReversibleScanner#previousRowInternal.
> {code}
>   private boolean previousRowInternal() {
> //...
> while (!beforeFirst) {
>   //
>   // what if currentRowNode is nub?
>   if (currentRowNode.hasOccurrences()) {// escape clause
> currentRowNode.resetFanIndex();
> return true;// found some values
>   }
> }
> {code}
> currentRowNode.hasOccurrences() only test whether it has cell or not. But in 
> the case of  currentRowNode.isNub() is true, previousRowInternal should 
> follow the previous fan instead of return.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (HBASE-19198) TestIPv6NIOServerSocketChannel fails; unable to bind

[stack (JIRA)]

stack created HBASE-19198:
-

 Summary: TestIPv6NIOServerSocketChannel fails; unable to bind
 Key: HBASE-19198
 URL: https://issues.apache.org/jira/browse/HBASE-19198
 Project: HBase
  Issue Type: Bug
  Components: test
Affects Versions: 2.0.0-beta-1
Reporter: stack
Assignee: stack
Priority: Minor


This test always fails on some hardware I have here abouts.

The test is sort of odd in that it asks to resolve 'localhost'. In my case, I 
get back two addresses: 127.0.0.1 and then a nonsense one, 205.127.0.0 which 
looks like a managled address.

I've tried to figure how resolve is broke on this machine but configs look good 
and dig/host using 'localhost' fails because it ain't an address to resolve.

Given latter, I'm changing the test to use getLocalHost which is what it is 
trying to look up



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-19128) Purge Distributed Log Replay from codebase, configurations, text; mark the feature as unsupported, broken.

[Appy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Appy updated HBASE-19128:
-
Attachment: HBASE-19128.master.003.patch

> Purge Distributed Log Replay from codebase, configurations, text; mark the 
> feature as unsupported, broken.
> --
>
> Key: HBASE-19128
> URL: https://issues.apache.org/jira/browse/HBASE-19128
> Project: HBase
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: stack
>Assignee: Appy
>  Labels: incompatible
> Fix For: 2.0.0
>
> Attachments: HBASE-19128.master.001.patch, 
> HBASE-19128.master.002.patch, HBASE-19128.master.003.patch
>
>
> Kill it. It keeps coming up and over again. Needs proper burial.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19102) TestZooKeeperMainServer fails with KeeperException$ConnectionLossException

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241484#comment-16241484
 ] 

Hudson commented on HBASE-19102:


SUCCESS: Integrated in Jenkins build HBase-1.3-IT #274 (See 
[https://builds.apache.org/job/HBase-1.3-IT/274/])
HBASE-19102 TestZooKeeperMainServer fails with KeeperException (stack: rev 
123f765eb408d5ccf3ed3e4a2cd247eb2c1bc305)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperMainServer.java


> TestZooKeeperMainServer fails with KeeperException$ConnectionLossException
> --
>
> Key: HBASE-19102
> URL: https://issues.apache.org/jira/browse/HBASE-19102
> Project: HBase
>  Issue Type: Bug
>Reporter: stack
>Assignee: stack
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1
>
> Attachments: HBASE-19102.master.001.patch, 
> HBASE-19102.master.002.patch, HBASE-19102.master.002.patch
>
>
> I'm trying to run test suite on a local machine. I never get to the second 
> part because I fail on below test with below exception near every time (and 
> an ipv6 test... will do that next).  
> 1 
> ---
>   2 Test set: org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   3 
> ---
>   4 Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 16.161 s 
> <<< FAILURE! - in org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   5 
> testCommandLineWorks(org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer)
>   Time elapsed: 15.848 s  <<< ERROR!
>   6 org.apache.zookeeper.KeeperException$ConnectionLossException: 
> KeeperErrorCode = ConnectionLoss for /testCommandLineWorks
>   7   at 
> org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer.testCommandLineWorks(TestZooKeeperMainServer.java:81)
> Looks like running the command before we are connected causes the above -- we 
> pause 15 seconds and then throw the above.   If I wait until connected before 
> proceding, stuff seems to work reliably. I don't have access to the watcher 
> on connections since we override the zk main class... so this seems only 
> avenue available at mo (This zk main thing is all a hack around zk main 
> because it had bugs ... but I think we have to keep the hack because folks 
> use different versions of zk. My $workplace defaults to something that is 
> years old, 3.4.5 for instance).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (HBASE-19164) Avoid UUID.randomUUID in tests

[Sahil Aggarwal (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241483#comment-16241483
 ] 

Sahil Aggarwal edited comment on HBASE-19164 at 11/7/17 4:53 AM:
-

I see multiple tests using 
{code:java}
UUID.randomUUID()
{code}
, do we just need to replace it with 
{code:java}
new UUID(ThreadLocalRandom.current().nextLong(), 
ThreadLocalRandom.current().nextLong()
{code}
)


was (Author: awked06):
I see multiple tests using ```UUID.randomUUID()```, do we just need to replace 
it with ```new UUID(ThreadLocalRandom.current().nextLong(), 
ThreadLocalRandom.current().nextLong())```

> Avoid UUID.randomUUID in tests
> --
>
> Key: HBASE-19164
> URL: https://issues.apache.org/jira/browse/HBASE-19164
> Project: HBase
>  Issue Type: Improvement
>  Components: test
>Reporter: Mike Drob
>  Labels: beginner
>
> We have a lot of places in our test code where we use {{UUID.randomUUID}} to 
> generate table names or paths for uniqueness. Unfortunately, this uses up a 
> good chunk of system entropy, since Sun chose that random UUID's should use 
> the NativePRNGBlocking implementation.
> We don't need to block on entropy for random bits to pick a random table name 
> in a test, so we can use something that doesn't strain the system too much - 
> secure random can be a source of problems on some VM or containers.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19164) Avoid UUID.randomUUID in tests

[Sahil Aggarwal (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241483#comment-16241483
 ] 

Sahil Aggarwal commented on HBASE-19164:


I see multiple tests using ```UUID.randomUUID()```, do we just need to replace 
it with ```new UUID(ThreadLocalRandom.current().nextLong(), 
ThreadLocalRandom.current().nextLong())```

> Avoid UUID.randomUUID in tests
> --
>
> Key: HBASE-19164
> URL: https://issues.apache.org/jira/browse/HBASE-19164
> Project: HBase
>  Issue Type: Improvement
>  Components: test
>Reporter: Mike Drob
>  Labels: beginner
>
> We have a lot of places in our test code where we use {{UUID.randomUUID}} to 
> generate table names or paths for uniqueness. Unfortunately, this uses up a 
> good chunk of system entropy, since Sun chose that random UUID's should use 
> the NativePRNGBlocking implementation.
> We don't need to block on entropy for random bits to pick a random table name 
> in a test, so we can use something that doesn't strain the system too much - 
> secure random can be a source of problems on some VM or containers.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19102) TestZooKeeperMainServer fails with KeeperException$ConnectionLossException

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241482#comment-16241482
 ] 

Hudson commented on HBASE-19102:


SUCCESS: Integrated in Jenkins build HBase-1.2-IT #1007 (See 
[https://builds.apache.org/job/HBase-1.2-IT/1007/])
HBASE-19102 TestZooKeeperMainServer fails with KeeperException (stack: rev 
498bcba095b7f108498d025e862a3bb741416b1d)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperMainServer.java


> TestZooKeeperMainServer fails with KeeperException$ConnectionLossException
> --
>
> Key: HBASE-19102
> URL: https://issues.apache.org/jira/browse/HBASE-19102
> Project: HBase
>  Issue Type: Bug
>Reporter: stack
>Assignee: stack
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1
>
> Attachments: HBASE-19102.master.001.patch, 
> HBASE-19102.master.002.patch, HBASE-19102.master.002.patch
>
>
> I'm trying to run test suite on a local machine. I never get to the second 
> part because I fail on below test with below exception near every time (and 
> an ipv6 test... will do that next).  
> 1 
> ---
>   2 Test set: org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   3 
> ---
>   4 Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 16.161 s 
> <<< FAILURE! - in org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   5 
> testCommandLineWorks(org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer)
>   Time elapsed: 15.848 s  <<< ERROR!
>   6 org.apache.zookeeper.KeeperException$ConnectionLossException: 
> KeeperErrorCode = ConnectionLoss for /testCommandLineWorks
>   7   at 
> org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer.testCommandLineWorks(TestZooKeeperMainServer.java:81)
> Looks like running the command before we are connected causes the above -- we 
> pause 15 seconds and then throw the above.   If I wait until connected before 
> proceding, stuff seems to work reliably. I don't have access to the watcher 
> on connections since we override the zk main class... so this seems only 
> avenue available at mo (This zk main thing is all a hack around zk main 
> because it had bugs ... but I think we have to keep the hack because folks 
> use different versions of zk. My $workplace defaults to something that is 
> years old, 3.4.5 for instance).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-16574) Add backup / restore feature to refguide

[Frank Welsch (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-16574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241480#comment-16241480
 ] 

Frank Welsch commented on HBASE-16574:
--

I can edit the text of any patches if you want. Just give me a few days to work 
on it if you send me anything.

> Add backup / restore feature to refguide
> 
>
> Key: HBASE-16574
> URL: https://issues.apache.org/jira/browse/HBASE-16574
> Project: HBase
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Vladimir Rodionov
>  Labels: backup
> Fix For: 2.0.0-beta-1
>
> Attachments: Backup-and-Restore-Apache_19Sep2016.pdf, 
> HBASE-16574.001.patch, HBASE-16574.002.patch, hbase_reference_guide.v1.pdf
>
>
> This issue is to add backup / restore feature description to hbase refguide.
> The description should cover:
> scenarios where backup / restore is used
> backup / restore commands and sample usage
> considerations in setup



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19102) TestZooKeeperMainServer fails with KeeperException$ConnectionLossException

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241478#comment-16241478
 ] 

Hudson commented on HBASE-19102:


FAILURE: Integrated in Jenkins build HBase-1.3-JDK7 #336 (See 
[https://builds.apache.org/job/HBase-1.3-JDK7/336/])
HBASE-19102 TestZooKeeperMainServer fails with KeeperException (stack: rev 
123f765eb408d5ccf3ed3e4a2cd247eb2c1bc305)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperMainServer.java


> TestZooKeeperMainServer fails with KeeperException$ConnectionLossException
> --
>
> Key: HBASE-19102
> URL: https://issues.apache.org/jira/browse/HBASE-19102
> Project: HBase
>  Issue Type: Bug
>Reporter: stack
>Assignee: stack
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1
>
> Attachments: HBASE-19102.master.001.patch, 
> HBASE-19102.master.002.patch, HBASE-19102.master.002.patch
>
>
> I'm trying to run test suite on a local machine. I never get to the second 
> part because I fail on below test with below exception near every time (and 
> an ipv6 test... will do that next).  
> 1 
> ---
>   2 Test set: org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   3 
> ---
>   4 Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 16.161 s 
> <<< FAILURE! - in org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   5 
> testCommandLineWorks(org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer)
>   Time elapsed: 15.848 s  <<< ERROR!
>   6 org.apache.zookeeper.KeeperException$ConnectionLossException: 
> KeeperErrorCode = ConnectionLoss for /testCommandLineWorks
>   7   at 
> org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer.testCommandLineWorks(TestZooKeeperMainServer.java:81)
> Looks like running the command before we are connected causes the above -- we 
> pause 15 seconds and then throw the above.   If I wait until connected before 
> proceding, stuff seems to work reliably. I don't have access to the watcher 
> on connections since we override the zk main class... so this seems only 
> avenue available at mo (This zk main thing is all a hack around zk main 
> because it had bugs ... but I think we have to keep the hack because folks 
> use different versions of zk. My $workplace defaults to something that is 
> years old, 3.4.5 for instance).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19102) TestZooKeeperMainServer fails with KeeperException$ConnectionLossException

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241476#comment-16241476
 ] 

Hudson commented on HBASE-19102:


FAILURE: Integrated in Jenkins build HBase-1.3-JDK8 #354 (See 
[https://builds.apache.org/job/HBase-1.3-JDK8/354/])
HBASE-19102 TestZooKeeperMainServer fails with KeeperException (stack: rev 
123f765eb408d5ccf3ed3e4a2cd247eb2c1bc305)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperMainServer.java


> TestZooKeeperMainServer fails with KeeperException$ConnectionLossException
> --
>
> Key: HBASE-19102
> URL: https://issues.apache.org/jira/browse/HBASE-19102
> Project: HBase
>  Issue Type: Bug
>Reporter: stack
>Assignee: stack
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1
>
> Attachments: HBASE-19102.master.001.patch, 
> HBASE-19102.master.002.patch, HBASE-19102.master.002.patch
>
>
> I'm trying to run test suite on a local machine. I never get to the second 
> part because I fail on below test with below exception near every time (and 
> an ipv6 test... will do that next).  
> 1 
> ---
>   2 Test set: org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   3 
> ---
>   4 Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 16.161 s 
> <<< FAILURE! - in org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   5 
> testCommandLineWorks(org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer)
>   Time elapsed: 15.848 s  <<< ERROR!
>   6 org.apache.zookeeper.KeeperException$ConnectionLossException: 
> KeeperErrorCode = ConnectionLoss for /testCommandLineWorks
>   7   at 
> org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer.testCommandLineWorks(TestZooKeeperMainServer.java:81)
> Looks like running the command before we are connected causes the above -- we 
> pause 15 seconds and then throw the above.   If I wait until connected before 
> proceding, stuff seems to work reliably. I don't have access to the watcher 
> on connections since we override the zk main class... so this seems only 
> avenue available at mo (This zk main thing is all a hack around zk main 
> because it had bugs ... but I think we have to keep the hack because folks 
> use different versions of zk. My $workplace defaults to something that is 
> years old, 3.4.5 for instance).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (HBASE-19197) Move version on branch-2 from 2.0.0-alpha4 to 2.0.0-beta-1.SNAPSHOT

[stack (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack resolved HBASE-19197.
---
Resolution: Fixed
  Assignee: stack

Pushed on branch-2.

> Move version on branch-2 from 2.0.0-alpha4 to 2.0.0-beta-1.SNAPSHOT
> ---
>
> Key: HBASE-19197
> URL: https://issues.apache.org/jira/browse/HBASE-19197
> Project: HBase
>  Issue Type: Sub-task
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0-beta-1
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (HBASE-19197) Move version on branch-2 from 2.0.0-alpha4 to 2.0.0-beta-1.SNAPSHOT

[stack (JIRA)]

stack created HBASE-19197:
-

 Summary: Move version on branch-2 from 2.0.0-alpha4 to 
2.0.0-beta-1.SNAPSHOT
 Key: HBASE-19197
 URL: https://issues.apache.org/jira/browse/HBASE-19197
 Project: HBase
  Issue Type: Sub-task
Reporter: stack






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19102) TestZooKeeperMainServer fails with KeeperException$ConnectionLossException

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241475#comment-16241475
 ] 

Hudson commented on HBASE-19102:


FAILURE: Integrated in Jenkins build HBase-1.2-JDK7 #268 (See 
[https://builds.apache.org/job/HBase-1.2-JDK7/268/])
HBASE-19102 TestZooKeeperMainServer fails with KeeperException (stack: rev 
498bcba095b7f108498d025e862a3bb741416b1d)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperMainServer.java


> TestZooKeeperMainServer fails with KeeperException$ConnectionLossException
> --
>
> Key: HBASE-19102
> URL: https://issues.apache.org/jira/browse/HBASE-19102
> Project: HBase
>  Issue Type: Bug
>Reporter: stack
>Assignee: stack
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1
>
> Attachments: HBASE-19102.master.001.patch, 
> HBASE-19102.master.002.patch, HBASE-19102.master.002.patch
>
>
> I'm trying to run test suite on a local machine. I never get to the second 
> part because I fail on below test with below exception near every time (and 
> an ipv6 test... will do that next).  
> 1 
> ---
>   2 Test set: org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   3 
> ---
>   4 Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 16.161 s 
> <<< FAILURE! - in org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   5 
> testCommandLineWorks(org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer)
>   Time elapsed: 15.848 s  <<< ERROR!
>   6 org.apache.zookeeper.KeeperException$ConnectionLossException: 
> KeeperErrorCode = ConnectionLoss for /testCommandLineWorks
>   7   at 
> org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer.testCommandLineWorks(TestZooKeeperMainServer.java:81)
> Looks like running the command before we are connected causes the above -- we 
> pause 15 seconds and then throw the above.   If I wait until connected before 
> proceding, stuff seems to work reliably. I don't have access to the watcher 
> on connections since we override the zk main class... so this seems only 
> avenue available at mo (This zk main thing is all a hack around zk main 
> because it had bugs ... but I think we have to keep the hack because folks 
> use different versions of zk. My $workplace defaults to something that is 
> years old, 3.4.5 for instance).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19102) TestZooKeeperMainServer fails with KeeperException$ConnectionLossException

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241474#comment-16241474
 ] 

Hudson commented on HBASE-19102:


FAILURE: Integrated in Jenkins build HBase-1.2-JDK8 #265 (See 
[https://builds.apache.org/job/HBase-1.2-JDK8/265/])
HBASE-19102 TestZooKeeperMainServer fails with KeeperException (stack: rev 
498bcba095b7f108498d025e862a3bb741416b1d)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperMainServer.java


> TestZooKeeperMainServer fails with KeeperException$ConnectionLossException
> --
>
> Key: HBASE-19102
> URL: https://issues.apache.org/jira/browse/HBASE-19102
> Project: HBase
>  Issue Type: Bug
>Reporter: stack
>Assignee: stack
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1
>
> Attachments: HBASE-19102.master.001.patch, 
> HBASE-19102.master.002.patch, HBASE-19102.master.002.patch
>
>
> I'm trying to run test suite on a local machine. I never get to the second 
> part because I fail on below test with below exception near every time (and 
> an ipv6 test... will do that next).  
> 1 
> ---
>   2 Test set: org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   3 
> ---
>   4 Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 16.161 s 
> <<< FAILURE! - in org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   5 
> testCommandLineWorks(org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer)
>   Time elapsed: 15.848 s  <<< ERROR!
>   6 org.apache.zookeeper.KeeperException$ConnectionLossException: 
> KeeperErrorCode = ConnectionLoss for /testCommandLineWorks
>   7   at 
> org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer.testCommandLineWorks(TestZooKeeperMainServer.java:81)
> Looks like running the command before we are connected causes the above -- we 
> pause 15 seconds and then throw the above.   If I wait until connected before 
> proceding, stuff seems to work reliably. I don't have access to the watcher 
> on connections since we override the zk main class... so this seems only 
> avenue available at mo (This zk main thing is all a hack around zk main 
> because it had bugs ... but I think we have to keep the hack because folks 
> use different versions of zk. My $workplace defaults to something that is 
> years old, 3.4.5 for instance).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-19196) Release hbase-2.0.0-beta-1; the "Finish-line" release

[stack (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack updated HBASE-19196:
--
Summary: Release hbase-2.0.0-beta-1; the "Finish-line" release  (was: 
Release hbase-2.0.0-beta-1; the "Finish" release)

> Release hbase-2.0.0-beta-1; the "Finish-line" release
> -
>
> Key: HBASE-19196
> URL: https://issues.apache.org/jira/browse/HBASE-19196
> Project: HBase
>  Issue Type: Bug
>Reporter: stack
> Fix For: 2.0.0-beta-1
>
>
> APIs done, but external facing and Coprocessors. Done w/ features. Bug fixes 
> only from here on out. There'll be a beta-2 but that is about rolling upgrade 
> and bug fixes only. Then our first 2.0.0 Release Candidate.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (HBASE-19102) TestZooKeeperMainServer fails with KeeperException$ConnectionLossException

[stack (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack resolved HBASE-19102.
---
Resolution: Fixed

Reresolve.

> TestZooKeeperMainServer fails with KeeperException$ConnectionLossException
> --
>
> Key: HBASE-19102
> URL: https://issues.apache.org/jira/browse/HBASE-19102
> Project: HBase
>  Issue Type: Bug
>Reporter: stack
>Assignee: stack
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1
>
> Attachments: HBASE-19102.master.001.patch, 
> HBASE-19102.master.002.patch, HBASE-19102.master.002.patch
>
>
> I'm trying to run test suite on a local machine. I never get to the second 
> part because I fail on below test with below exception near every time (and 
> an ipv6 test... will do that next).  
> 1 
> ---
>   2 Test set: org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   3 
> ---
>   4 Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 16.161 s 
> <<< FAILURE! - in org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   5 
> testCommandLineWorks(org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer)
>   Time elapsed: 15.848 s  <<< ERROR!
>   6 org.apache.zookeeper.KeeperException$ConnectionLossException: 
> KeeperErrorCode = ConnectionLoss for /testCommandLineWorks
>   7   at 
> org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer.testCommandLineWorks(TestZooKeeperMainServer.java:81)
> Looks like running the command before we are connected causes the above -- we 
> pause 15 seconds and then throw the above.   If I wait until connected before 
> proceding, stuff seems to work reliably. I don't have access to the watcher 
> on connections since we override the zk main class... so this seems only 
> avenue available at mo (This zk main thing is all a hack around zk main 
> because it had bugs ... but I think we have to keep the hack because folks 
> use different versions of zk. My $workplace defaults to something that is 
> years old, 3.4.5 for instance).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-19102) TestZooKeeperMainServer fails with KeeperException$ConnectionLossException

[stack (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack updated HBASE-19102:
--
Fix Version/s: 1.2.7
   1.3.2
   1.4.0

> TestZooKeeperMainServer fails with KeeperException$ConnectionLossException
> --
>
> Key: HBASE-19102
> URL: https://issues.apache.org/jira/browse/HBASE-19102
> Project: HBase
>  Issue Type: Bug
>Reporter: stack
>Assignee: stack
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1
>
> Attachments: HBASE-19102.master.001.patch, 
> HBASE-19102.master.002.patch, HBASE-19102.master.002.patch
>
>
> I'm trying to run test suite on a local machine. I never get to the second 
> part because I fail on below test with below exception near every time (and 
> an ipv6 test... will do that next).  
> 1 
> ---
>   2 Test set: org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   3 
> ---
>   4 Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 16.161 s 
> <<< FAILURE! - in org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   5 
> testCommandLineWorks(org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer)
>   Time elapsed: 15.848 s  <<< ERROR!
>   6 org.apache.zookeeper.KeeperException$ConnectionLossException: 
> KeeperErrorCode = ConnectionLoss for /testCommandLineWorks
>   7   at 
> org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer.testCommandLineWorks(TestZooKeeperMainServer.java:81)
> Looks like running the command before we are connected causes the above -- we 
> pause 15 seconds and then throw the above.   If I wait until connected before 
> proceding, stuff seems to work reliably. I don't have access to the watcher 
> on connections since we override the zk main class... so this seems only 
> avenue available at mo (This zk main thing is all a hack around zk main 
> because it had bugs ... but I think we have to keep the hack because folks 
> use different versions of zk. My $workplace defaults to something that is 
> years old, 3.4.5 for instance).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19102) TestZooKeeperMainServer fails with KeeperException$ConnectionLossException

[stack (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241472#comment-16241472
 ] 

stack commented on HBASE-19102:
---

Pushed to branch-1.2 => branch-1 with all branches in between.

> TestZooKeeperMainServer fails with KeeperException$ConnectionLossException
> --
>
> Key: HBASE-19102
> URL: https://issues.apache.org/jira/browse/HBASE-19102
> Project: HBase
>  Issue Type: Bug
>Reporter: stack
>Assignee: stack
> Fix For: 1.4.0, 1.3.2, 1.2.7, 2.0.0-beta-1
>
> Attachments: HBASE-19102.master.001.patch, 
> HBASE-19102.master.002.patch, HBASE-19102.master.002.patch
>
>
> I'm trying to run test suite on a local machine. I never get to the second 
> part because I fail on below test with below exception near every time (and 
> an ipv6 test... will do that next).  
> 1 
> ---
>   2 Test set: org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   3 
> ---
>   4 Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 16.161 s 
> <<< FAILURE! - in org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   5 
> testCommandLineWorks(org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer)
>   Time elapsed: 15.848 s  <<< ERROR!
>   6 org.apache.zookeeper.KeeperException$ConnectionLossException: 
> KeeperErrorCode = ConnectionLoss for /testCommandLineWorks
>   7   at 
> org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer.testCommandLineWorks(TestZooKeeperMainServer.java:81)
> Looks like running the command before we are connected causes the above -- we 
> pause 15 seconds and then throw the above.   If I wait until connected before 
> proceding, stuff seems to work reliably. I don't have access to the watcher 
> on connections since we override the zk main class... so this seems only 
> avenue available at mo (This zk main thing is all a hack around zk main 
> because it had bugs ... but I think we have to keep the hack because folks 
> use different versions of zk. My $workplace defaults to something that is 
> years old, 3.4.5 for instance).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Reopened] (HBASE-19102) TestZooKeeperMainServer fails with KeeperException$ConnectionLossException

[stack (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack reopened HBASE-19102:
---

Reopening to backport this fix. It fails for me on local machine.

> TestZooKeeperMainServer fails with KeeperException$ConnectionLossException
> --
>
> Key: HBASE-19102
> URL: https://issues.apache.org/jira/browse/HBASE-19102
> Project: HBase
>  Issue Type: Bug
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19102.master.001.patch, 
> HBASE-19102.master.002.patch, HBASE-19102.master.002.patch
>
>
> I'm trying to run test suite on a local machine. I never get to the second 
> part because I fail on below test with below exception near every time (and 
> an ipv6 test... will do that next).  
> 1 
> ---
>   2 Test set: org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   3 
> ---
>   4 Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 16.161 s 
> <<< FAILURE! - in org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
>   5 
> testCommandLineWorks(org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer)
>   Time elapsed: 15.848 s  <<< ERROR!
>   6 org.apache.zookeeper.KeeperException$ConnectionLossException: 
> KeeperErrorCode = ConnectionLoss for /testCommandLineWorks
>   7   at 
> org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer.testCommandLineWorks(TestZooKeeperMainServer.java:81)
> Looks like running the command before we are connected causes the above -- we 
> pause 15 seconds and then throw the above.   If I wait until connected before 
> proceding, stuff seems to work reliably. I don't have access to the watcher 
> on connections since we override the zk main class... so this seems only 
> avenue available at mo (This zk main thing is all a hack around zk main 
> because it had bugs ... but I think we have to keep the hack because folks 
> use different versions of zk. My $workplace defaults to something that is 
> years old, 3.4.5 for instance).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-18467) nightly job needs to comment on jira

[stack (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-18467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241465#comment-16241465
 ] 

stack commented on HBASE-18467:
---

How I help here [~busbey] ? We need nightlies passing before you'll push the 
patch here?

> nightly job needs to comment on jira
> 
>
> Key: HBASE-18467
> URL: https://issues.apache.org/jira/browse/HBASE-18467
> Project: HBase
>  Issue Type: Improvement
>  Components: community, test
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Critical
> Attachments: HBASE-18467.0.WIP.patch, HBASE-18467.0.patch, 
> HBASE-18467.1.patch
>
>
> follow on from HBASE-18147, need a post action that pings all newly-committed 
> jiras with result of the branch build



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19195) More error-prone fixes

[stack (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241450#comment-16241450
 ] 

stack commented on HBASE-19195:
---

+1

> More error-prone fixes
> --
>
> Key: HBASE-19195
> URL: https://issues.apache.org/jira/browse/HBASE-19195
> Project: HBase
>  Issue Type: Bug
>Reporter: Mike Drob
>Assignee: Mike Drob
> Attachments: HBASE-19195.patch
>
>
> Next batch. Getting close to the end, I think...
> Patch to fix the rest of the issues in hbase-client, -mapreduce, and -server 
> forthcoming.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-19009) implement enable/disableTableReplication for AsyncAdmin

[Guanghao Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19009:
---
Attachment: HBASE-19009.master.005.patch

> implement enable/disableTableReplication for AsyncAdmin
> ---
>
> Key: HBASE-19009
> URL: https://issues.apache.org/jira/browse/HBASE-19009
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Fix For: 3.0.0, 2.0.0-beta-1
>
> Attachments: HBASE-19009.master.001.patch, 
> HBASE-19009.master.002.patch, HBASE-19009.master.003.patch, 
> HBASE-19009.master.004.patch, HBASE-19009.master.005.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-18722) Replace copied guava code w/ pointer to the (shaded) lib

[Asim Zafir (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-18722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241446#comment-16241446
 ] 

Asim Zafir commented on HBASE-18722:


I am in process of finalizing this. I will take care of it. 



> Replace copied guava code w/ pointer to the (shaded) lib
> 
>
> Key: HBASE-18722
> URL: https://issues.apache.org/jira/browse/HBASE-18722
> Project: HBase
>  Issue Type: Bug
>Reporter: stack
>Priority: Minor
>  Labels: beginner
>
> I found a few bits of code copied from guava src:
> {code}
> ./src/main/java/org/apache/hadoop/hbase/io/LimitInputStream.java: * Copied 
> from guava source code v15 (LimitedInputStream)
> ./src/main/java/org/apache/hadoop/hbase/io/LimitInputStream.java: * allows to 
> be compatible with guava 11 to 15+.
> ./src/main/java/org/apache/hadoop/hbase/util/ByteBufferUtils.java: * 
> from guava v21
> ./src/main/java/org/apache/hadoop/hbase/util/Bytes.java: * 
> comparator from guava v21
> {code}
> We can instead point back at guava implementations now we use shaded guava 
> internally. No point having it in our code base when latest guava is on 
> latest CLASSPATH (This wasn't always the case; this is why the code was 
> copied into hbase).
> Also, there are other copies other than the above.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-18233) We shouldn't wait for readlock in doMiniBatchMutation in case of deadlock

[stack (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-18233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241445#comment-16241445
 ] 

stack commented on HBASE-18233:
---

Thanks [~carp84] Let me try your args (I was just -PrunAllTests). Mine is 
physical machine too... similar.

> We shouldn't wait for readlock in doMiniBatchMutation in case of deadlock
> -
>
> Key: HBASE-18233
> URL: https://issues.apache.org/jira/browse/HBASE-18233
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 1.2.7
>Reporter: Allan Yang
>Assignee: Allan Yang
>Priority: Blocker
> Fix For: 1.3.2, 1.2.7
>
> Attachments: HBASE-18233-branch-1.2.patch, 
> HBASE-18233-branch-1.2.trivial.patch, HBASE-18233-branch-1.2.v2.patch, 
> HBASE-18233-branch-1.2.v3.patch, HBASE-18233-branch-1.2.v4 (1).patch, 
> HBASE-18233-branch-1.2.v4 (1).patch, HBASE-18233-branch-1.2.v4 (2).patch, 
> HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v4.patch, 
> HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v4.patch, 
> HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v4.patch, 
> HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v4.patch, 
> HBASE-18233-branch-1.2.v5.patch, HBASE-18233-branch-1.2.v5.patch, 
> HBASE-18233.branch-1.2.UT.log
>
>
> Please refer to the discuss in HBASE-18144
> https://issues.apache.org/jira/browse/HBASE-18144?focusedCommentId=16051701=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16051701



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-18722) Replace copied guava code w/ pointer to the (shaded) lib

[Sahil Aggarwal (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-18722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241444#comment-16241444
 ] 

Sahil Aggarwal commented on HBASE-18722:


[~azafir] You working on it or shall i take it up?

> Replace copied guava code w/ pointer to the (shaded) lib
> 
>
> Key: HBASE-18722
> URL: https://issues.apache.org/jira/browse/HBASE-18722
> Project: HBase
>  Issue Type: Bug
>Reporter: stack
>Priority: Minor
>  Labels: beginner
>
> I found a few bits of code copied from guava src:
> {code}
> ./src/main/java/org/apache/hadoop/hbase/io/LimitInputStream.java: * Copied 
> from guava source code v15 (LimitedInputStream)
> ./src/main/java/org/apache/hadoop/hbase/io/LimitInputStream.java: * allows to 
> be compatible with guava 11 to 15+.
> ./src/main/java/org/apache/hadoop/hbase/util/ByteBufferUtils.java: * 
> from guava v21
> ./src/main/java/org/apache/hadoop/hbase/util/Bytes.java: * 
> comparator from guava v21
> {code}
> We can instead point back at guava implementations now we use shaded guava 
> internally. No point having it in our code base when latest guava is on 
> latest CLASSPATH (This wasn't always the case; this is why the code was 
> copied into hbase).
> Also, there are other copies other than the above.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-19196) Release hbase-2.0.0-beta-1; the "Finish" release

[stack (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack updated HBASE-19196:
--
Fix Version/s: 2.0.0-beta-1

> Release hbase-2.0.0-beta-1; the "Finish" release
> 
>
> Key: HBASE-19196
> URL: https://issues.apache.org/jira/browse/HBASE-19196
> Project: HBase
>  Issue Type: Bug
>Reporter: stack
> Fix For: 2.0.0-beta-1
>
>
> APIs done, but external facing and Coprocessors. Done w/ features. Bug fixes 
> only from here on out. There'll be a beta-2 but that is about rolling upgrade 
> and bug fixes only. Then our first 2.0.0 Release Candidate.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (HBASE-19196) Release hbase-2.0.0-beta-1; the "Finish" release

[stack (JIRA)]

stack created HBASE-19196:
-

 Summary: Release hbase-2.0.0-beta-1; the "Finish" release
 Key: HBASE-19196
 URL: https://issues.apache.org/jira/browse/HBASE-19196
 Project: HBase
  Issue Type: Bug
Reporter: stack


APIs done, but external facing and Coprocessors. Done w/ features. Bug fixes 
only from here on out. There'll be a beta-2 but that is about rolling upgrade 
and bug fixes only. Then our first 2.0.0 Release Candidate.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (HBASE-18844) Release hbase-2.0.0-alpha-4; Theme "Coprocessor API Cleanup"

[stack (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-18844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack resolved HBASE-18844.
---
Resolution: Fixed

Pushed out the release today (Thanks for kick [~mdrob])

> Release hbase-2.0.0-alpha-4; Theme "Coprocessor API Cleanup"
> 
>
> Key: HBASE-18844
> URL: https://issues.apache.org/jira/browse/HBASE-18844
> Project: HBase
>  Issue Type: Bug
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0-alpha-4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-18974) Document "Becoming a Committer"

[Yu Li (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-18974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241437#comment-16241437
 ] 

Yu Li commented on HBASE-18974:
---

IMHO first some general criteria then some detailed instructions is better. 
Such as the hadoop doc:
* A history of sustained contribution to the project
* High-quality contributions
* Community involvement

I think "sustained" and "high-quality" should be a requirement for 
"contributions" (or please correct me if not bosses). Current list given in 
patch seems more like detailed scope of "contribution" and "community 
involvement" to me (smile).

> Document "Becoming a Committer"
> ---
>
> Key: HBASE-18974
> URL: https://issues.apache.org/jira/browse/HBASE-18974
> Project: HBase
>  Issue Type: Bug
>  Components: community, documentation
>Reporter: Mike Drob
>Assignee: Mike Drob
> Attachments: HBASE-18974.patch, HBASE-18974.v2.patch
>
>
> Based on the mailing list discussion at 
> https://lists.apache.org/thread.html/81c633cbe1f6f78421cbdad5b9549643c67803a723a9d86a513264c0@%3Cdev.hbase.apache.org%3E
>  it sounds like we should record some of the thoughts for future contributors 
> to refer to.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (HBASE-19128) Purge Distributed Log Replay from codebase, configurations, text; mark the feature as unsupported, broken.

[Appy (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16240845#comment-16240845
 ] 

Appy edited comment on HBASE-19128 at 11/7/17 3:42 AM:
---

I tend to note down things which are important or worth highlighting or out of 
obvious when dealing with new stuff, so anyone following the work and familiar 
with these code parts can quickly validate the work. Here's the list (i'll keep 
updating it as we go):
- RecoveringRegionWatcher: We create it's instance in HRegionServer, but never 
use it.
- I see "hbase.master.distributed.log.replay" in 
https://github.com/apache/hbase/blob/master/src/main/asciidoc/_chapters/hbase-default.adoc,
 but not in [hbase book's default 
configs|http://hbase.apache.org/book.html#config.files]. Why?
- We were advertising in one places that DLR is On by default - [hbase-default 
ascii 
doc|https://github.com/apache/hbase/blob/master/src/main/asciidoc/_chapters/hbase-default.adoc]
- The configuration "hbase.master.distributed.log.replay" is never used in 
non-test code! Which I think is both good and bad.
Good --> No one can be using DLR right now (even if they set the config to 
true), so no upgrade issues. Bad --> It's simply weird!
- Although RSRpcServices#replay was added as part of DLR, it's now also used by 
RegionReplicas. So can't delete that.
{noformat}
  @QosPriority(priority = HConstants.REPLAY_QOS)
  public ReplicateWALEntryResponse replay(final RpcController controller,
  final ReplicateWALEntryRequest request) throws ServiceException {
{noformat}



Removal is combination of HBASE-7006 and HBASE-13121 ([~enis])


was (Author: appy):
I tend to note down things which are important or worth highlighting or out of 
obvious when dealing with new stuff, so anyone following the work and familiar 
with these code parts can quickly validate the work. Here's the list (i'll keep 
updating it as we go):
- RecoveringRegionWatcher: We create it's instance in HRegionServer, but never 
use it.
- I see "hbase.master.distributed.log.replay" in 
https://github.com/apache/hbase/blob/master/src/main/asciidoc/_chapters/hbase-default.adoc,
 but not in [hbase book's default 
configs|http://hbase.apache.org/book.html#config.files]. Why?
- We were advertising in one places that DLR is On by default - [hbase-default 
ascii 
doc|https://github.com/apache/hbase/blob/master/src/main/asciidoc/_chapters/hbase-default.adoc]
- The configuration "hbase.master.distributed.log.replay" is never used in 
non-test code! Which I think is both good and bad.
Good --> No one can be using DLR right now (even if they set the config to 
true), so no upgrade issues. Bad --> It's simply weird!



Removal is combination of HBASE-7006 and HBASE-13121 ([~enis])

> Purge Distributed Log Replay from codebase, configurations, text; mark the 
> feature as unsupported, broken.
> --
>
> Key: HBASE-19128
> URL: https://issues.apache.org/jira/browse/HBASE-19128
> Project: HBase
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: stack
>Assignee: Appy
>  Labels: incompatible
> Fix For: 2.0.0
>
> Attachments: HBASE-19128.master.001.patch, 
> HBASE-19128.master.002.patch
>
>
> Kill it. It keeps coming up and over again. Needs proper burial.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19075) Task tabs on master UI cause page scroll

[Sahil Aggarwal (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241435#comment-16241435
 ] 

Sahil Aggarwal commented on HBASE-19075:


I had to do "Submit Patch" to move it to "Path Available", earlier i submitted 
patch by just attaching the file.

> Task tabs on master UI cause page scroll
> 
>
> Key: HBASE-19075
> URL: https://issues.apache.org/jira/browse/HBASE-19075
> Project: HBase
>  Issue Type: Bug
>  Components: master
>Reporter: Mike Drob
>Assignee: Sahil Aggarwal
>  Labels: beginner
> Fix For: 2.0.0
>
> Attachments: HBASE-19075.master.001.patch
>
>
> On the master info page, the clicking the tabs under Tasks causes the page to 
> scroll back to the top of the page.
> {noformat}
> Tasks
> Show All Monitored Tasks Show non-RPC Tasks Show All RPC Handler Tasks Show 
> Active RPC Calls Show Client Operations View as JSON
> {noformat}
> ^^ Any of those
> The other tab-like links on the page keep the scroll in the same location.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19009) implement enable/disableTableReplication for AsyncAdmin

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241436#comment-16241436
 ] 

Hadoop QA commented on HBASE-19009:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  2m 
55s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m  
0s{color} | {color:blue} Findbugs executables are not available. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green}  0m  
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green}  0m 
 0s{color} | {color:green} The patch appears to include 2 new or modified test 
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
30s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  6m 
11s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
21s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
53s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  7m 
20s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m  
4s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
14s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red}  1m 
48s{color} | {color:red} root in the patch failed. {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red}  0m 
24s{color} | {color:red} hbase-client in the patch failed. {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red}  0m 
50s{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red}  0m 24s{color} 
| {color:red} hbase-client in the patch failed. {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red}  0m 50s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
35s{color} | {color:red} hbase-client: The patch generated 22 new + 251 
unchanged - 3 fixed = 273 total (was 254) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  1m 
12s{color} | {color:red} hbase-server: The patch generated 2 new + 3 unchanged 
- 2 fixed = 5 total (was 5) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:red}-1{color} | {color:red} shadedjars {color} | {color:red}  2m 
17s{color} | {color:red} patch has 14 errors when building our shaded 
downstream artifacts. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red}  3m 
45s{color} | {color:red} The patch causes 15 errors with Hadoop v2.6.1. {color} 
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red}  5m  
4s{color} | {color:red} The patch causes 15 errors with Hadoop v2.6.2. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red}  6m 
20s{color} | {color:red} The patch causes 15 errors with Hadoop v2.6.3. {color} 
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red}  7m 
46s{color} | {color:red} The patch causes 15 errors with Hadoop v2.6.4. {color} 
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red}  9m  
5s{color} | {color:red} The patch causes 15 errors with Hadoop v2.6.5. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 10m 
28s{color} | {color:red} The patch causes 15 errors with Hadoop v2.7.1. {color} 
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 11m 
50s{color} | {color:red} The patch causes 15 errors with Hadoop v2.7.2. {color} 
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 13m 
10s{color} | {color:red} The patch causes 15 errors with Hadoop v2.7.3. {color} 
|
| {color:red}-1{color} | {color:red} 

[jira] [Updated] (HBASE-19075) Task tabs on master UI cause page scroll

[Sahil Aggarwal (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sahil Aggarwal updated HBASE-19075:
---
Status: Patch Available  (was: Open)

> Task tabs on master UI cause page scroll
> 
>
> Key: HBASE-19075
> URL: https://issues.apache.org/jira/browse/HBASE-19075
> Project: HBase
>  Issue Type: Bug
>  Components: master
>Reporter: Mike Drob
>Assignee: Sahil Aggarwal
>  Labels: beginner
> Fix For: 2.0.0
>
> Attachments: HBASE-19075.master.001.patch
>
>
> On the master info page, the clicking the tabs under Tasks causes the page to 
> scroll back to the top of the page.
> {noformat}
> Tasks
> Show All Monitored Tasks Show non-RPC Tasks Show All RPC Handler Tasks Show 
> Active RPC Calls Show Client Operations View as JSON
> {noformat}
> ^^ Any of those
> The other tab-like links on the page keep the scroll in the same location.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19128) Purge Distributed Log Replay from codebase, configurations, text; mark the feature as unsupported, broken.

[Appy (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241434#comment-16241434
 ] 

Appy commented on HBASE-19128:
--

Just going over QA failures (fixing tests), some self-added cleanup TODOs, old 
patches to make sure i didn't miss anything obvious, etc.

> Purge Distributed Log Replay from codebase, configurations, text; mark the 
> feature as unsupported, broken.
> --
>
> Key: HBASE-19128
> URL: https://issues.apache.org/jira/browse/HBASE-19128
> Project: HBase
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: stack
>Assignee: Appy
>  Labels: incompatible
> Fix For: 2.0.0
>
> Attachments: HBASE-19128.master.001.patch, 
> HBASE-19128.master.002.patch
>
>
> Kill it. It keeps coming up and over again. Needs proper burial.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work stopped] (HBASE-19075) Task tabs on master UI cause page scroll

[Sahil Aggarwal (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on HBASE-19075 stopped by Sahil Aggarwal.
--
> Task tabs on master UI cause page scroll
> 
>
> Key: HBASE-19075
> URL: https://issues.apache.org/jira/browse/HBASE-19075
> Project: HBase
>  Issue Type: Bug
>  Components: master
>Reporter: Mike Drob
>Assignee: Sahil Aggarwal
>  Labels: beginner
> Fix For: 2.0.0
>
> Attachments: HBASE-19075.master.001.patch
>
>
> On the master info page, the clicking the tabs under Tasks causes the page to 
> scroll back to the top of the page.
> {noformat}
> Tasks
> Show All Monitored Tasks Show non-RPC Tasks Show All RPC Handler Tasks Show 
> Active RPC Calls Show Client Operations View as JSON
> {noformat}
> ^^ Any of those
> The other tab-like links on the page keep the scroll in the same location.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-18233) We shouldn't wait for readlock in doMiniBatchMutation in case of deadlock

[Yu Li (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-18233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yu Li updated HBASE-18233:
--
Attachment: HBASE-18233.branch-1.2.UT.log

Attaching the result against latest branch-1.2 code base (SHA: 4e9136e03) w/ 
patch, using below command:
{noformat}
mvn -B -PrunAllTests\
 -DreuseForks=false\
 -Dmaven.test.redirectTestOutputToFile=true\
 -Dsurefire.rerunFailingTestsCount=2\
 -Dit.test=noItTest\
 -Dmaven.test.failure.ignore=true\
 -Dsurefire.testFailureIgnore=true\
 -Dmaven.test.error.ignore=true\
 clean test
{noformat}
And the result lgtm (hbase-server for example):
{noformat}
first part:
[INFO] Results:
[INFO]
[WARNING] Tests run: 1022, Failures: 0, Errors: 0, Skipped: 20

second part:
[INFO] Results:
[INFO]
[WARNING] Tests run: 2561, Failures: 0, Errors: 0, Skipped: 40
{noformat}

Used a physical machine for UT, with 64GB memory and 24core cpu

> We shouldn't wait for readlock in doMiniBatchMutation in case of deadlock
> -
>
> Key: HBASE-18233
> URL: https://issues.apache.org/jira/browse/HBASE-18233
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 1.2.7
>Reporter: Allan Yang
>Assignee: Allan Yang
>Priority: Blocker
> Fix For: 1.3.2, 1.2.7
>
> Attachments: HBASE-18233-branch-1.2.patch, 
> HBASE-18233-branch-1.2.trivial.patch, HBASE-18233-branch-1.2.v2.patch, 
> HBASE-18233-branch-1.2.v3.patch, HBASE-18233-branch-1.2.v4 (1).patch, 
> HBASE-18233-branch-1.2.v4 (1).patch, HBASE-18233-branch-1.2.v4 (2).patch, 
> HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v4.patch, 
> HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v4.patch, 
> HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v4.patch, 
> HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v4.patch, 
> HBASE-18233-branch-1.2.v5.patch, HBASE-18233-branch-1.2.v5.patch, 
> HBASE-18233.branch-1.2.UT.log
>
>
> Please refer to the discuss in HBASE-18144
> https://issues.apache.org/jira/browse/HBASE-18144?focusedCommentId=16051701=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16051701



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-19195) More error-prone fixes

[Mike Drob (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mike Drob updated HBASE-19195:
--
Attachment: HBASE-19195.patch

> More error-prone fixes
> --
>
> Key: HBASE-19195
> URL: https://issues.apache.org/jira/browse/HBASE-19195
> Project: HBase
>  Issue Type: Bug
>Reporter: Mike Drob
>Assignee: Mike Drob
> Attachments: HBASE-19195.patch
>
>
> Next batch. Getting close to the end, I think...
> Patch to fix the rest of the issues in hbase-client, -mapreduce, and -server 
> forthcoming.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-19195) More error-prone fixes

[Mike Drob (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mike Drob updated HBASE-19195:
--
Status: Patch Available  (was: Open)

> More error-prone fixes
> --
>
> Key: HBASE-19195
> URL: https://issues.apache.org/jira/browse/HBASE-19195
> Project: HBase
>  Issue Type: Bug
>Reporter: Mike Drob
>Assignee: Mike Drob
> Attachments: HBASE-19195.patch
>
>
> Next batch. Getting close to the end, I think...
> Patch to fix the rest of the issues in hbase-client, -mapreduce, and -server 
> forthcoming.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (HBASE-19195) More error-prone fixes

[Mike Drob (JIRA)]

Mike Drob created HBASE-19195:
-

 Summary: More error-prone fixes
 Key: HBASE-19195
 URL: https://issues.apache.org/jira/browse/HBASE-19195
 Project: HBase
  Issue Type: Bug
Reporter: Mike Drob
Assignee: Mike Drob


Next batch. Getting close to the end, I think...

Patch to fix the rest of the issues in hbase-client, -mapreduce, and -server 
forthcoming.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-18844) Release hbase-2.0.0-alpha-4; Theme "Coprocessor API Cleanup"

[Mike Drob (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-18844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241415#comment-16241415
 ] 

Mike Drob commented on HBASE-18844:
---

We're good here, right?

> Release hbase-2.0.0-alpha-4; Theme "Coprocessor API Cleanup"
> 
>
> Key: HBASE-18844
> URL: https://issues.apache.org/jira/browse/HBASE-18844
> Project: HBase
>  Issue Type: Bug
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0-alpha-4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-19194) TestRSGroupsBase has some always false checks

[Mike Drob (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mike Drob updated HBASE-19194:
--
Summary: TestRSGroupsBase has some always false checks  (was: 
TestRSGroupsBase has some always true checks)

> TestRSGroupsBase has some always false checks
> -
>
> Key: HBASE-19194
> URL: https://issues.apache.org/jira/browse/HBASE-19194
> Project: HBase
>  Issue Type: Bug
>  Components: rsgroup, test
>Reporter: Mike Drob
> Fix For: 3.0.0, 2.0.0-beta-1
>
>
> Discovered via error-prone analysis:
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.6.1:testCompile 
> (default-testCompile) on project hbase-rsgroup: Compilation failure: 
> Compilation failure:
> [ERROR] 
> /Users/mdrob/IdeaProjects/hbase/hbase-rsgroup/src/test/java/org/apache/hadoop/hbase/rsgroup/TestRSGroupsBase.java:[421,40]
>  [CollectionIncompatibleType] Argument 'region' should not be passed to this 
> method; its type RegionInfo is not compatible with its collection's type 
> argument String
> [ERROR] (see http://errorprone.info/bugpattern/CollectionIncompatibleType)
> [ERROR] 
> /Users/mdrob/IdeaProjects/hbase/hbase-rsgroup/src/test/java/org/apache/hadoop/hbase/rsgroup/TestRSGroupsBase.java:[531,65]
>  [CollectionIncompatibleType] Argument 'targetRegion' should not be passed to 
> this method; its type String is not compatible with its collection's type 
> argument RegionInfo
> [ERROR] (see http://errorprone.info/bugpattern/CollectionIncompatibleType)
> {noformat}
> Both of these are checks to {{List.contains}} with an element of the wrong 
> type so they will always return false. The first is an optimization that we 
> can probably live without (or short circuit on the Master, at least) the 
> second is an assertion that will never fail, rendering the test ineffective.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (HBASE-19194) TestRSGroupsBase has some always true checks

[Mike Drob (JIRA)]

Mike Drob created HBASE-19194:
-

 Summary: TestRSGroupsBase has some always true checks
 Key: HBASE-19194
 URL: https://issues.apache.org/jira/browse/HBASE-19194
 Project: HBase
  Issue Type: Bug
  Components: rsgroup, test
Reporter: Mike Drob
 Fix For: 3.0.0, 2.0.0-beta-1


Discovered via error-prone analysis:

{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.6.1:testCompile 
(default-testCompile) on project hbase-rsgroup: Compilation failure: 
Compilation failure:
[ERROR] 
/Users/mdrob/IdeaProjects/hbase/hbase-rsgroup/src/test/java/org/apache/hadoop/hbase/rsgroup/TestRSGroupsBase.java:[421,40]
 [CollectionIncompatibleType] Argument 'region' should not be passed to this 
method; its type RegionInfo is not compatible with its collection's type 
argument String
[ERROR] (see http://errorprone.info/bugpattern/CollectionIncompatibleType)
[ERROR] 
/Users/mdrob/IdeaProjects/hbase/hbase-rsgroup/src/test/java/org/apache/hadoop/hbase/rsgroup/TestRSGroupsBase.java:[531,65]
 [CollectionIncompatibleType] Argument 'targetRegion' should not be passed to 
this method; its type String is not compatible with its collection's type 
argument RegionInfo
[ERROR] (see http://errorprone.info/bugpattern/CollectionIncompatibleType)
{noformat}

Both of these are checks to {{List.contains}} with an element of the wrong 
type so they will always return false. The first is an optimization that we can 
probably live without (or short circuit on the Master, at least) the second is 
an assertion that will never fail, rendering the test ineffective.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-19009) implement enable/disableTableReplication for AsyncAdmin

[Guanghao Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19009:
---
Fix Version/s: 3.0.0

> implement enable/disableTableReplication for AsyncAdmin
> ---
>
> Key: HBASE-19009
> URL: https://issues.apache.org/jira/browse/HBASE-19009
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Fix For: 3.0.0, 2.0.0-beta-1
>
> Attachments: HBASE-19009.master.001.patch, 
> HBASE-19009.master.002.patch, HBASE-19009.master.003.patch, 
> HBASE-19009.master.004.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-19009) implement enable/disableTableReplication for AsyncAdmin

[Guanghao Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19009:
---
Attachment: HBASE-19009.master.004.patch

> implement enable/disableTableReplication for AsyncAdmin
> ---
>
> Key: HBASE-19009
> URL: https://issues.apache.org/jira/browse/HBASE-19009
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19009.master.001.patch, 
> HBASE-19009.master.002.patch, HBASE-19009.master.003.patch, 
> HBASE-19009.master.004.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19128) Purge Distributed Log Replay from codebase, configurations, text; mark the feature as unsupported, broken.

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241367#comment-16241367
 ] 

Hadoop QA commented on HBASE-19128:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  2m 
33s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m  
0s{color} | {color:blue} Findbugs executables are not available. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green}  0m  
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green}  0m 
 0s{color} | {color:green} The patch appears to include 25 new or modified test 
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
29s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
35s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  6m 
27s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  4m 
50s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  9m 
 6s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  4m 
56s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
12s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  6m  
6s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green}  6m  
6s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  6m  
6s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
 9s{color} | {color:green} The patch hbase-protocol-shaded passed checkstyle 
{color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
21s{color} | {color:green} The patch hbase-common passed checkstyle {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
 8s{color} | {color:green} The patch hbase-hadoop-compat passed checkstyle 
{color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
 9s{color} | {color:green} hbase-hadoop2-compat: The patch generated 0 new + 0 
unchanged - 1 fixed = 0 total (was 1) {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
 8s{color} | {color:green} The patch hbase-protocol passed checkstyle {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
27s{color} | {color:green} hbase-client: The patch generated 0 new + 456 
unchanged - 2 fixed = 456 total (was 458) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  1m  
4s{color} | {color:red} hbase-server: The patch generated 5 new + 1297 
unchanged - 102 fixed = 1302 total (was 1399) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  2m 
14s{color} | {color:red} root: The patch generated 5 new + 1757 unchanged - 105 
fixed = 1762 total (was 1862) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green}  0m  
1s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  4m 
11s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
46m  3s{color} | {color:green} Patch does not cause any errors with Hadoop 
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| 

[jira] [Comment Edited] (HBASE-19146) Hbase3.0 protobuf-maven-plugin do not support Arm64(only for x86)

[Yuqi Gu (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241363#comment-16241363
 ] 

Yuqi Gu edited comment on HBASE-19146 at 11/7/17 2:22 AM:
--

There are no Arm64 binaries on Maven Central.( 
https://repo.maven.apache.org/maven2/com/google/protobuf/protoc/)

I raise a [ticket |https://github.com/google/protobuf/issues/3844]in protobuf 
project and ask them to include Arm64 binaries in the next release.

Then ' ' in pom.xml will be modified for called Arm64 protoc.


was (Author: yqgu):
There are no Arm64 binaries on Maven Central.( 
https://repo.maven.apache.org/maven2/com/google/protobuf/protoc/)

I raise a [ticket |https://github.com/google/protobuf/issues/3844]in protobuf 
project and ask them to include AARCH64 binaries in the next release.

Then ' ' in pom.xml will be modified for called Arm64 protoc.

> Hbase3.0  protobuf-maven-plugin do not support Arm64(only for x86)
> --
>
> Key: HBASE-19146
> URL: https://issues.apache.org/jira/browse/HBASE-19146
> Project: HBase
>  Issue Type: Bug
>  Components: build, pom
>Affects Versions: 3.0.0
> Environment: OS:  Ubuntu 16.04.3 
> OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-2ubuntu1.16.04.3-b11)
> Hw platform:  AARCH64
>Reporter: Yuqi Gu
>
> We are building the HBase 3.0.0-SNAPSHOT on AARCH64.
> It is noted that 'protobuf-maven-plugin' only support x86 shown as follows:
> {code:java}
>  
>org.xolstice.maven.plugins
>protobuf-maven-plugin
>${protobuf.plugin.version}
>
>   com.google.protobuf:protoc:${external.protobuf.version}:
> exe:${os.detected.classifier}
> 
> com.google.protobuf:protoc:${external.protobuf.version}:exe:${os.detected.classifier}
> 
>false
>true
>   
> 
> {code}
> So the build is failed.
> {code:java}
> [INFO] --- protobuf-maven-plugin:0.5.0:compile (compile-protoc) @ 
> hbase-protocol-shaded ---
> [INFO] Compiling 32 proto file(s) to 
> /root/hbase/hbase-protocol-shaded/target/generated-sources/protobuf/java
> Failed to execute goal 
> org.xolstice.maven.plugins:protobuf-maven-plugin:0.5.0:compile 
> (compile-protoc) on project hbase-protocol-shaded: Missing:
> {code}
> Then I installed aarch64 protobuf 2.5.0 on the host and modify the pom:
> {code:java}
> -   ${basedir}/src/main/protobuf/
> +  /usr/local/bin/protoc
> {code}
>  The build is also failed:
> {code:java}
> [INFO] Compiling 32 proto file(s) to 
> /root/hbase/hbase-protocol-shaded/target/generated-sources/protobuf/java
> [ERROR] PROTOC FAILED: google/protobuf/any.proto:31:10: Unrecognized syntax 
> identifier "proto3".  This parser only recognizes "proto2".
> {code}
> It seems that "internal.protobuf.version" in "hbase-protocol-shaded" is 3.3.0.
> How to fix it? Thanks!
>   



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-19035) Miss metrics when coprocessor use region scanner to read data

[Guanghao Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19035:
---
Description: 
Region interface is exposed to coprocessor. So coprocessor use getScanner to 
get a region scanner to read data. But the scan metrics was only updated in 
region server level. So we will miss some scan metrics for the read from 
coprocessor.

|| Region Operation || When to update requests metric ||
| get | update read metric in nextRaw() |
| put | update write metric in batchMutate() |
| delete | update write metric in batchMutate() |
| increment | update read metric by get() and  update write metric in doDelta() 
|
| append | update read metric by get() and  update write metric in doDelta() |
| mutateRow | update write metric in processRowsWithLocks() |
| mutateRowsWithLocks | update write metric in processRowsWithLocks() |
| batchMutate | update write metric in batchMutate() |
| checkAndMutate | update read metric by get() and  update write metric by 
mutateRow() |
| checkAndRowMutate | update read metric by get() and  update write metric by 
doBatchMutate() |
| processRowsWithLocks | update write metric in processRowsWithLocks() |

1. Move read requests to region level. Because RegionScanner exposed to CP.
2. Update write requests count in processRowsWithLocks. This was missed in 
previous implemenation, too.
3. Remove requestRowActionCount in RSRpcServices. This metric can be computed 
by region's readRequestsCount and writeRequestsCount.

Upload to review board: https://reviews.apache.org/r/63579/

  was:
Region interface is exposed to coprocessor. So coprocessor use getScanner to 
get a region scanner to read data. But the scan metrics was only updated in 
region server level. So we will miss some scan metrics for the read from 
coprocessor.

|| Region Operation || When to update requests metric ||
| get | update read metric in nextRaw() |
| put | update write metric in batchMutate() |
| delete | update write metric in batchMutate() |
| increment | update read metric by get() and  update write metric in doDelta() 
|
| append | update read metric by get() and  update write metric in doDelta() |
| mutateRow | update write metric in processRowsWithLocks() |
| mutateRowsWithLocks | update write metric in processRowsWithLocks() |
| batchMutate | update write metric in batchMutate() |
| checkAndMutate | update read metric by get() and  update write metric by 
mutateRow() |
| checkAndRowMutate | update read metric by get() and  update write metric by 
doBatchMutate() |
| processRowsWithLocks | update write metric in processRowsWithLocks() |

1. Move read requests to region level. Because RegionScanner exposed to CP.
2. Update write requests count in processRowsWithLocks. This was missed in 
previous implemenation, too.
3. Remove requestRowActionCount in RSRpcServices. This metric can be computed 
by region's readRequestsCount and writeRequestsCount.


> Miss metrics when coprocessor use region scanner to read data
> -
>
> Key: HBASE-19035
> URL: https://issues.apache.org/jira/browse/HBASE-19035
> Project: HBase
>  Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19035.master.001.patch, 
> HBASE-19035.master.002.patch
>
>
> Region interface is exposed to coprocessor. So coprocessor use getScanner to 
> get a region scanner to read data. But the scan metrics was only updated in 
> region server level. So we will miss some scan metrics for the read from 
> coprocessor.
> || Region Operation || When to update requests metric ||
> | get | update read metric in nextRaw() |
> | put | update write metric in batchMutate() |
> | delete | update write metric in batchMutate() |
> | increment | update read metric by get() and  update write metric in 
> doDelta() |
> | append | update read metric by get() and  update write metric in doDelta() |
> | mutateRow | update write metric in processRowsWithLocks() |
> | mutateRowsWithLocks | update write metric in processRowsWithLocks() |
> | batchMutate | update write metric in batchMutate() |
> | checkAndMutate | update read metric by get() and  update write metric by 
> mutateRow() |
> | checkAndRowMutate | update read metric by get() and  update write metric by 
> doBatchMutate() |
> | processRowsWithLocks | update write metric in processRowsWithLocks() |
> 1. Move read requests to region level. Because RegionScanner exposed to CP.
> 2. Update write requests count in processRowsWithLocks. This was missed in 
> previous implemenation, too.
> 3. Remove requestRowActionCount in RSRpcServices. This metric can be computed 
> by region's readRequestsCount and writeRequestsCount.
> Upload to review board: https://reviews.apache.org/r/63579/



--

[jira] [Updated] (HBASE-19035) Miss metrics when coprocessor use region scanner to read data

[Guanghao Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19035:
---
Description: 
Region interface is exposed to coprocessor. So coprocessor use getScanner to 
get a region scanner to read data. But the scan metrics was only updated in 
region server level. So we will miss some scan metrics for the read from 
coprocessor.

|| Region Operation || When to update requests metric ||
| get | update read metric in nextRaw() |
| put | update write metric in batchMutate() |
| delete | update write metric in batchMutate() |
| increment | update read metric by get() and  update write metric in doDelta() 
|
| append | update read metric by get() and  update write metric in doDelta() |
| mutateRow | update write metric in processRowsWithLocks() |
| mutateRowsWithLocks | update write metric in processRowsWithLocks() |
| batchMutate | update write metric in batchMutate() |
| checkAndMutate | update read metric by get() and  update write metric by 
mutateRow() |
| checkAndRowMutate | update read metric by get() and  update write metric by 
doBatchMutate() |
| processRowsWithLocks | update write metric in processRowsWithLocks() |

1. Move read requests to region level. Because RegionScanner exposed to CP.
2. Update write requests count in processRowsWithLocks. This was missed in 
previous implemenation, too.
3. Remove requestRowActionCount in RSRpcServices. This metric can be computed 
by region's readRequestsCount and writeRequestsCount.

  was:
Region interface is exposed to coprocessor. So coprocessor use getScanner to 
get a region scanner to read data. But the scan metrics was only updated in 
region server level. So we will miss some scan metrics for the read from 
coprocessor.

|| Region Operation || When to update requests metric ||
| get | update read metric in nextRaw() |
| put | update write metric in batchMutate() |
| delete | update write metric in batchMutate() |
| increment | update read metric by get() and  update write metric in doDelta() 
|
| append | update read metric by get() and  update write metric in doDelta() |
| mutateRow | update write metric in processRowsWithLocks() |
| mutateRowsWithLocks | update write metric in processRowsWithLocks() |
| batchMutate | update write metric in batchMutate() |
| checkAndMutate | update read metric by get() and  update write metric by 
mutateRow() |
| checkAndRowMutate | update read metric by get() and  update write metric by 
doBatchMutate() |
| processRowsWithLocks | update write metric in processRowsWithLocks() |

Meanwhile, remove requestRowActionCount in RSRpcServices. This metric can be 
computed by region's readRequestsCount and writeRequestsCount.


> Miss metrics when coprocessor use region scanner to read data
> -
>
> Key: HBASE-19035
> URL: https://issues.apache.org/jira/browse/HBASE-19035
> Project: HBase
>  Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19035.master.001.patch, 
> HBASE-19035.master.002.patch
>
>
> Region interface is exposed to coprocessor. So coprocessor use getScanner to 
> get a region scanner to read data. But the scan metrics was only updated in 
> region server level. So we will miss some scan metrics for the read from 
> coprocessor.
> || Region Operation || When to update requests metric ||
> | get | update read metric in nextRaw() |
> | put | update write metric in batchMutate() |
> | delete | update write metric in batchMutate() |
> | increment | update read metric by get() and  update write metric in 
> doDelta() |
> | append | update read metric by get() and  update write metric in doDelta() |
> | mutateRow | update write metric in processRowsWithLocks() |
> | mutateRowsWithLocks | update write metric in processRowsWithLocks() |
> | batchMutate | update write metric in batchMutate() |
> | checkAndMutate | update read metric by get() and  update write metric by 
> mutateRow() |
> | checkAndRowMutate | update read metric by get() and  update write metric by 
> doBatchMutate() |
> | processRowsWithLocks | update write metric in processRowsWithLocks() |
> 1. Move read requests to region level. Because RegionScanner exposed to CP.
> 2. Update write requests count in processRowsWithLocks. This was missed in 
> previous implemenation, too.
> 3. Remove requestRowActionCount in RSRpcServices. This metric can be computed 
> by region's readRequestsCount and writeRequestsCount.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19146) Hbase3.0 protobuf-maven-plugin do not support Arm64(only for x86)

[Yuqi Gu (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241363#comment-16241363
 ] 

Yuqi Gu commented on HBASE-19146:
-

There are no Arm64 binaries on Maven Central.( 
https://repo.maven.apache.org/maven2/com/google/protobuf/protoc/)

I raise a [ticket |https://github.com/google/protobuf/issues/3844]in protobuf 
project and ask them to include AARCH64 binaries in the next release.

Then ' ' in pom.xml will be modified for called Arm64 protoc.

> Hbase3.0  protobuf-maven-plugin do not support Arm64(only for x86)
> --
>
> Key: HBASE-19146
> URL: https://issues.apache.org/jira/browse/HBASE-19146
> Project: HBase
>  Issue Type: Bug
>  Components: build, pom
>Affects Versions: 3.0.0
> Environment: OS:  Ubuntu 16.04.3 
> OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-2ubuntu1.16.04.3-b11)
> Hw platform:  AARCH64
>Reporter: Yuqi Gu
>
> We are building the HBase 3.0.0-SNAPSHOT on AARCH64.
> It is noted that 'protobuf-maven-plugin' only support x86 shown as follows:
> {code:java}
>  
>org.xolstice.maven.plugins
>protobuf-maven-plugin
>${protobuf.plugin.version}
>
>   com.google.protobuf:protoc:${external.protobuf.version}:
> exe:${os.detected.classifier}
> 
> com.google.protobuf:protoc:${external.protobuf.version}:exe:${os.detected.classifier}
> 
>false
>true
>   
> 
> {code}
> So the build is failed.
> {code:java}
> [INFO] --- protobuf-maven-plugin:0.5.0:compile (compile-protoc) @ 
> hbase-protocol-shaded ---
> [INFO] Compiling 32 proto file(s) to 
> /root/hbase/hbase-protocol-shaded/target/generated-sources/protobuf/java
> Failed to execute goal 
> org.xolstice.maven.plugins:protobuf-maven-plugin:0.5.0:compile 
> (compile-protoc) on project hbase-protocol-shaded: Missing:
> {code}
> Then I installed aarch64 protobuf 2.5.0 on the host and modify the pom:
> {code:java}
> -   ${basedir}/src/main/protobuf/
> +  /usr/local/bin/protoc
> {code}
>  The build is also failed:
> {code:java}
> [INFO] Compiling 32 proto file(s) to 
> /root/hbase/hbase-protocol-shaded/target/generated-sources/protobuf/java
> [ERROR] PROTOC FAILED: google/protobuf/any.proto:31:10: Unrecognized syntax 
> identifier "proto3".  This parser only recognizes "proto2".
> {code}
> It seems that "internal.protobuf.version" in "hbase-protocol-shaded" is 3.3.0.
> How to fix it? Thanks!
>   



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-12091) Optionally ignore edits for dropped tables for replication.

[Andrew Purtell (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241361#comment-16241361
 ] 

Andrew Purtell commented on HBASE-12091:


Thanks. I'd like to roll the 1.4.0 RC0 tomorrow so if we can commit this by 
tomorrow it can make it in. 

> Optionally ignore edits for dropped tables for replication.
> ---
>
> Key: HBASE-12091
> URL: https://issues.apache.org/jira/browse/HBASE-12091
> Project: HBase
>  Issue Type: Bug
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
> Fix For: 1.4.0
>
> Attachments: 12091-branch-2.patch, 12091-v2-branch-1.txt, 
> 12091-v3-branch-1.txt, 12091-v4-branch-1.txt, 12091-v5-branch-1.txt, 
> 12091-v6-branch-1.txt, 12091.txt
>
>
> We just ran into a scenario where we dropped a table from both the source and 
> the sink, but the source still has outstanding edits that now it could not 
> get rid of. Now all replication is backed up behind these unreplicatable 
> edits.
> We should have an option to ignore edits for tables dropped at the source.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19165) TODO Handle stuck in transition: rit=OPENING, location=ve0538....

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241360#comment-16241360
 ] 

Hadoop QA commented on HBASE-19165:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  2m 
17s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m  
0s{color} | {color:blue} Findbugs executables are not available. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green}  0m  
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green}  0m 
 0s{color} | {color:green} The patch appears to include 1 new or modified test 
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  5m 
 4s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
43s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
 1s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  5m 
32s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
28s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
26s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
43s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
43s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  1m  
2s{color} | {color:red} hbase-server: The patch generated 1 new + 40 unchanged 
- 1 fixed = 41 total (was 41) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 1s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  4m 
27s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
45m 50s{color} | {color:green} Patch does not cause any errors with Hadoop 
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
33s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 99m 51s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
17s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}166m 56s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.master.procedure.TestTruncateTableProcedure 
|
|   | hadoop.hbase.master.procedure.TestCloneSnapshotProcedure |
|   | hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures |
|   | hadoop.hbase.master.procedure.TestCreateTableProcedure |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-19165 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12896287/HBASE-19165.master.002.patch
 |
| Optional Tests |  asflicense  javac  javadoc  unit  findbugs  shadedjars  
hadoopcheck  hbaseanti  checkstyle  compile  |
| uname | Linux 0d4866f01504 3.13.0-129-generic #178-Ubuntu SMP Fri Aug 11 
12:48:20 UTC 2017 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
 |
| git revision | master / 2a99b87af2 |
| maven | version: Apache Maven 3.5.2 
(138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z) |
| Default Java | 1.8.0_151 |
| checkstyle | 
https://builds.apache.org/job/PreCommit-HBASE-Build/9642/artifact/patchprocess/diff-checkstyle-hbase-server.txt
 |
| unit | 

[jira] [Updated] (HBASE-19186) Unify to use bytes to show size in master/rs ui

[Guanghao Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19186:
---
Fix Version/s: 2.0.0-beta-1
   3.0.0

> Unify to use bytes to show size in master/rs ui
> ---
>
> Key: HBASE-19186
> URL: https://issues.apache.org/jira/browse/HBASE-19186
> Project: HBase
>  Issue Type: Improvement
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Minor
> Fix For: 3.0.0, 2.0.0-beta-1
>
> Attachments: HBASE-19186.master.001.patch, master-process.png, 
> procedure-wal-state.png, procedure-wal-sync-stats.png, 
> regions-storefiles.png, regionserver-blockcache.png, regionserver-memory.png, 
> regionserver-process.png, regionserver-storefiles.png, 
> server-metrics-memory.png, server-metrics-storefiles.png
>
>
> 1. 10K ==> 10KB or 10M ==> 10MB or 10G => 10GB
> 2. remove "in bytes" in description



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (HBASE-19186) Unify to use bytes to show size in master/rs ui

[Guanghao Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241354#comment-16241354
 ] 

Guanghao Zhang edited comment on HBASE-19186 at 11/7/17 2:12 AM:
-

Pushed to branch-2 and master. Thanks all for reviewing.


was (Author: zghaobac):
Pushed to branch-2 and master.

> Unify to use bytes to show size in master/rs ui
> ---
>
> Key: HBASE-19186
> URL: https://issues.apache.org/jira/browse/HBASE-19186
> Project: HBase
>  Issue Type: Improvement
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Minor
> Fix For: 3.0.0, 2.0.0-beta-1
>
> Attachments: HBASE-19186.master.001.patch, master-process.png, 
> procedure-wal-state.png, procedure-wal-sync-stats.png, 
> regions-storefiles.png, regionserver-blockcache.png, regionserver-memory.png, 
> regionserver-process.png, regionserver-storefiles.png, 
> server-metrics-memory.png, server-metrics-storefiles.png
>
>
> 1. 10K ==> 10KB or 10M ==> 10MB or 10G => 10GB
> 2. remove "in bytes" in description



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-19186) Unify to use bytes to show size in master/rs ui

[Guanghao Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19186:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Pushed to branch-2 and master.

> Unify to use bytes to show size in master/rs ui
> ---
>
> Key: HBASE-19186
> URL: https://issues.apache.org/jira/browse/HBASE-19186
> Project: HBase
>  Issue Type: Improvement
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Minor
> Attachments: HBASE-19186.master.001.patch, master-process.png, 
> procedure-wal-state.png, procedure-wal-sync-stats.png, 
> regions-storefiles.png, regionserver-blockcache.png, regionserver-memory.png, 
> regionserver-process.png, regionserver-storefiles.png, 
> server-metrics-memory.png, server-metrics-storefiles.png
>
>
> 1. 10K ==> 10KB or 10M ==> 10MB or 10G => 10GB
> 2. remove "in bytes" in description



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (HBASE-19186) Unify to use bytes to show size in master/rs ui

[Guanghao Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-19186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241337#comment-16241337
 ] 

Guanghao Zhang commented on HBASE-19186:


Thanks [~appy] for reviewing. Attach screenshots to show the ui result.

> Unify to use bytes to show size in master/rs ui
> ---
>
> Key: HBASE-19186
> URL: https://issues.apache.org/jira/browse/HBASE-19186
> Project: HBase
>  Issue Type: Improvement
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Minor
> Attachments: HBASE-19186.master.001.patch, master-process.png, 
> procedure-wal-state.png, procedure-wal-sync-stats.png, 
> regions-storefiles.png, regionserver-blockcache.png, regionserver-memory.png, 
> regionserver-process.png, regionserver-storefiles.png, 
> server-metrics-memory.png, server-metrics-storefiles.png
>
>
> 1. 10K ==> 10KB or 10M ==> 10MB or 10G => 10GB
> 2. remove "in bytes" in description



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-19103) Add BigDecimalComparator for filter

[Qilin Cao (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Qilin Cao updated HBASE-19103:
--
Fix Version/s: (was: 1.2.0)
 Release Note: If BigDecimal is stored as value, and you need to add a 
matched comparator to the value filter when scanning, a BigDecimalComparator 
can be used.

I already fill out the release note, thks! 

> Add BigDecimalComparator for filter
> ---
>
> Key: HBASE-19103
> URL: https://issues.apache.org/jira/browse/HBASE-19103
> Project: HBase
>  Issue Type: New Feature
>  Components: Client
>Reporter: Qilin Cao
>Assignee: Qilin Cao
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: HBASE-19103-1.2.0-v1.patch, HBASE-19103-1.2.0-v2.patch, 
> HBASE-19103-trunk-v1.patch, HBASE-19103-trunk-v2.patch, 
> HBASE-19103-trunk-v3.patch
>
>
> Should I add BigDecimalComparator for filter? Some scenarios need to 
> calculate the data accurately may use it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)