[jira] [Updated] (HBASE-19925) Delete an unreachable peer will triggers all regionservers abort
[
https://issues.apache.org/jira/browse/HBASE-19925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-19925:
-
Assignee: Yun Zhao
Status: Patch Available (was: Open)
> Delete an unreachable peer will triggers all regionservers abort
>
>
> Key: HBASE-19925
> URL: https://issues.apache.org/jira/browse/HBASE-19925
> Project: HBase
> Issue Type: Bug
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Critical
> Attachments: HBASE-19925.master.001.patch
>
>
> Add an unreachable peer
> {code:java}
> add_peer '4', CLUSTER_KEY => "server1.cie.com:2181:/hbase"{code}
> After a while to delete it,Regionserver will appear in the following log and
> stop.
> {code:java}
> 2018-02-02 20:04:25,959 INFO [main-EventThread.replicationSource,4]
> regionserver.ReplicationSource: Replicating
> 5467de52-dc46-45be-902c-110dd7a83e06 -> null
> 2018-02-02 20:04:25,960 ERROR
> [main-EventThread.replicationSource,4.replicationSource..com%2C16020%2C1515498473547.default,4]
> regionserver.ReplicationSource: Unexpected exception in
> ReplicationSourceWorkerThread, currentPath=null
> java.lang.IllegalArgumentException: Peer with id= 4 is not connected
> at
> org.apache.hadoop.hbase.replication.ReplicationPeersZKImpl.getStatusOfPeer(ReplicationPeersZKImpl.java:207)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.isPeerEnabled(ReplicationSource.java:327)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource$ReplicationSourceWorkerThread.run(ReplicationSource.java:512)
> 2018-02-02 20:04:25,960 INFO
> [main-EventThread.replicationSource,4.replicationSource..com%2C16020%2C1515498473547.default,4]
> regionserver.HRegionServer: STOPPED: Unexpected exception in
> ReplicationSourceWorkerThread{code}
>
> HBase 1.2.6
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-19925) Delete an unreachable peer will triggers all regionservers abort
[
https://issues.apache.org/jira/browse/HBASE-19925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-19925:
-
Attachment: HBASE-19925.master.001.patch
> Delete an unreachable peer will triggers all regionservers abort
>
>
> Key: HBASE-19925
> URL: https://issues.apache.org/jira/browse/HBASE-19925
> Project: HBase
> Issue Type: Bug
>Reporter: Yun Zhao
>Priority: Critical
> Attachments: HBASE-19925.master.001.patch
>
>
> Add an unreachable peer
> {code:java}
> add_peer '4', CLUSTER_KEY => "server1.cie.com:2181:/hbase"{code}
> After a while to delete it,Regionserver will appear in the following log and
> stop.
> {code:java}
> 2018-02-02 20:04:25,959 INFO [main-EventThread.replicationSource,4]
> regionserver.ReplicationSource: Replicating
> 5467de52-dc46-45be-902c-110dd7a83e06 -> null
> 2018-02-02 20:04:25,960 ERROR
> [main-EventThread.replicationSource,4.replicationSource..com%2C16020%2C1515498473547.default,4]
> regionserver.ReplicationSource: Unexpected exception in
> ReplicationSourceWorkerThread, currentPath=null
> java.lang.IllegalArgumentException: Peer with id= 4 is not connected
> at
> org.apache.hadoop.hbase.replication.ReplicationPeersZKImpl.getStatusOfPeer(ReplicationPeersZKImpl.java:207)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.isPeerEnabled(ReplicationSource.java:327)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource$ReplicationSourceWorkerThread.run(ReplicationSource.java:512)
> 2018-02-02 20:04:25,960 INFO
> [main-EventThread.replicationSource,4.replicationSource..com%2C16020%2C1515498473547.default,4]
> regionserver.HRegionServer: STOPPED: Unexpected exception in
> ReplicationSourceWorkerThread{code}
>
> HBase 1.2.6
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19925) Delete an unreachable peer will triggers all regionservers abort
[
https://issues.apache.org/jira/browse/HBASE-19925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16351235#comment-16351235
]
Yun Zhao commented on HBASE-19925:
--
[~yuzhih...@gmail.com]
It is really because of this.
However, when the ReplicationSource terminating, Should not start a new
ReplicationSourceWorkerThread / ReplicationSourceShipper thread.
And this thread will reconnect zookeeeper, Cause zookeeper SendThread can not
stop.
> Delete an unreachable peer will triggers all regionservers abort
>
>
> Key: HBASE-19925
> URL: https://issues.apache.org/jira/browse/HBASE-19925
> Project: HBase
> Issue Type: Bug
>Reporter: Yun Zhao
>Priority: Critical
> Attachments: HBASE-19925.master.001.patch
>
>
> Add an unreachable peer
> {code:java}
> add_peer '4', CLUSTER_KEY => "server1.cie.com:2181:/hbase"{code}
> After a while to delete it,Regionserver will appear in the following log and
> stop.
> {code:java}
> 2018-02-02 20:04:25,959 INFO [main-EventThread.replicationSource,4]
> regionserver.ReplicationSource: Replicating
> 5467de52-dc46-45be-902c-110dd7a83e06 -> null
> 2018-02-02 20:04:25,960 ERROR
> [main-EventThread.replicationSource,4.replicationSource..com%2C16020%2C1515498473547.default,4]
> regionserver.ReplicationSource: Unexpected exception in
> ReplicationSourceWorkerThread, currentPath=null
> java.lang.IllegalArgumentException: Peer with id= 4 is not connected
> at
> org.apache.hadoop.hbase.replication.ReplicationPeersZKImpl.getStatusOfPeer(ReplicationPeersZKImpl.java:207)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.isPeerEnabled(ReplicationSource.java:327)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource$ReplicationSourceWorkerThread.run(ReplicationSource.java:512)
> 2018-02-02 20:04:25,960 INFO
> [main-EventThread.replicationSource,4.replicationSource..com%2C16020%2C1515498473547.default,4]
> regionserver.HRegionServer: STOPPED: Unexpected exception in
> ReplicationSourceWorkerThread{code}
>
> HBase 1.2.6
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-19925) Delete an unreachable peer will triggers all regionservers abort
[
https://issues.apache.org/jira/browse/HBASE-19925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-19925:
-
Description:
Add an unreachable peer
{code:java}
add_peer '4', CLUSTER_KEY => "server1.cie.com:2181:/hbase"{code}
After a while to delete it,Regionserver will appear in the following log and
stop.
{code:java}
2018-02-02 20:04:25,959 INFO [main-EventThread.replicationSource,4]
regionserver.ReplicationSource: Replicating
5467de52-dc46-45be-902c-110dd7a83e06 -> null
2018-02-02 20:04:25,960 ERROR
[main-EventThread.replicationSource,4.replicationSource..com%2C16020%2C1515498473547.default,4]
regionserver.ReplicationSource: Unexpected exception in
ReplicationSourceWorkerThread, currentPath=null
java.lang.IllegalArgumentException: Peer with id= 4 is not connected
at
org.apache.hadoop.hbase.replication.ReplicationPeersZKImpl.getStatusOfPeer(ReplicationPeersZKImpl.java:207)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.isPeerEnabled(ReplicationSource.java:327)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource$ReplicationSourceWorkerThread.run(ReplicationSource.java:512)
2018-02-02 20:04:25,960 INFO
[main-EventThread.replicationSource,4.replicationSource..com%2C16020%2C1515498473547.default,4]
regionserver.HRegionServer: STOPPED: Unexpected exception in
ReplicationSourceWorkerThread{code}
HBase 1.2.6
was:
Add an unreachable peer
{code:java}
add_peer '4', CLUSTER_KEY => "server1.cie.com:2181:/hbase"{code}
After a while to delete it,Regionserver will appear in the following log and
stop.
{code:java}
2018-02-02 20:04:25,959 INFO [main-EventThread.replicationSource,4]
regionserver.ReplicationSource: Replicating
5467de52-dc46-45be-902c-110dd7a83e06 -> null
2018-02-02 20:04:25,960 ERROR
[main-EventThread.replicationSource,4.replicationSource..com%2C16020%2C1515498473547.default,4]
regionserver.ReplicationSource: Unexpected exception in
ReplicationSourceWorkerThread, currentPath=null
java.lang.IllegalArgumentException: Peer with id= 4 is not connected
at
org.apache.hadoop.hbase.replication.ReplicationPeersZKImpl.getStatusOfPeer(ReplicationPeersZKImpl.java:207)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.isPeerEnabled(ReplicationSource.java:327)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource$ReplicationSourceWorkerThread.run(ReplicationSource.java:512)
2018-02-02 20:04:25,960 INFO
[main-EventThread.replicationSource,4.replicationSource..com%2C16020%2C1515498473547.default,4]
regionserver.HRegionServer: STOPPED: Unexpected exception in
ReplicationSourceWorkerThread{code}
> Delete an unreachable peer will triggers all regionservers abort
>
>
> Key: HBASE-19925
> URL: https://issues.apache.org/jira/browse/HBASE-19925
> Project: HBase
> Issue Type: Bug
>Reporter: Yun Zhao
>Priority: Critical
>
> Add an unreachable peer
> {code:java}
> add_peer '4', CLUSTER_KEY => "server1.cie.com:2181:/hbase"{code}
> After a while to delete it,Regionserver will appear in the following log and
> stop.
> {code:java}
> 2018-02-02 20:04:25,959 INFO [main-EventThread.replicationSource,4]
> regionserver.ReplicationSource: Replicating
> 5467de52-dc46-45be-902c-110dd7a83e06 -> null
> 2018-02-02 20:04:25,960 ERROR
> [main-EventThread.replicationSource,4.replicationSource..com%2C16020%2C1515498473547.default,4]
> regionserver.ReplicationSource: Unexpected exception in
> ReplicationSourceWorkerThread, currentPath=null
> java.lang.IllegalArgumentException: Peer with id= 4 is not connected
> at
> org.apache.hadoop.hbase.replication.ReplicationPeersZKImpl.getStatusOfPeer(ReplicationPeersZKImpl.java:207)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.isPeerEnabled(ReplicationSource.java:327)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource$ReplicationSourceWorkerThread.run(ReplicationSource.java:512)
> 2018-02-02 20:04:25,960 INFO
> [main-EventThread.replicationSource,4.replicationSource..com%2C16020%2C1515498473547.default,4]
> regionserver.HRegionServer: STOPPED: Unexpected exception in
> ReplicationSourceWorkerThread{code}
>
> HBase 1.2.6
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-19925) Delete an unreachable peer will triggers all regionservers abort
Yun Zhao created HBASE-19925:
Summary: Delete an unreachable peer will triggers all
regionservers abort
Key: HBASE-19925
URL: https://issues.apache.org/jira/browse/HBASE-19925
Project: HBase
Issue Type: Bug
Reporter: Yun Zhao
Add an unreachable peer
{code:java}
add_peer '4', CLUSTER_KEY => "server1.cie.com:2181:/hbase"{code}
After a while to delete it,Regionserver will appear in the following log and
stop.
{code:java}
2018-02-02 20:04:25,959 INFO [main-EventThread.replicationSource,4]
regionserver.ReplicationSource: Replicating
5467de52-dc46-45be-902c-110dd7a83e06 -> null
2018-02-02 20:04:25,960 ERROR
[main-EventThread.replicationSource,4.replicationSource..com%2C16020%2C1515498473547.default,4]
regionserver.ReplicationSource: Unexpected exception in
ReplicationSourceWorkerThread, currentPath=null
java.lang.IllegalArgumentException: Peer with id= 4 is not connected
at
org.apache.hadoop.hbase.replication.ReplicationPeersZKImpl.getStatusOfPeer(ReplicationPeersZKImpl.java:207)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.isPeerEnabled(ReplicationSource.java:327)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource$ReplicationSourceWorkerThread.run(ReplicationSource.java:512)
2018-02-02 20:04:25,960 INFO
[main-EventThread.replicationSource,4.replicationSource..com%2C16020%2C1515498473547.default,4]
regionserver.HRegionServer: STOPPED: Unexpected exception in
ReplicationSourceWorkerThread{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19226) Limit the reduce tasks number of incremental load
[ https://issues.apache.org/jira/browse/HBASE-19226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16249082#comment-16249082 ] Yun Zhao commented on HBASE-19226: -- The number of regions in the same table also changes, and the reduce tasks number also needs to be dynamically adjusted. 0.005 a bit too small, generally should be in the range of 0.1 to 1. Add a specified number is ok, but how to judge with ratio :( [~reidchan] > Limit the reduce tasks number of incremental load > - > > Key: HBASE-19226 > URL: https://issues.apache.org/jira/browse/HBASE-19226 > Project: HBase > Issue Type: Improvement >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Minor > Attachments: HBASE-19226.master.001.patch, > HBASE-19226.master.002.patch > > > When using MapReduce job to perform an incremental load into a table,the > number of reduce tasks is the current number of regions. If there are too > many regions, will lead to network+disk I/O is too large, affecting the > real-time request. > Need to use a configuration to set a number or ratio? > Limit running reduce tasks since > [https://issues.apache.org/jira/browse/MAPREDUCE-5583], the old version can > only be set reduce number. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19226) Limit the reduce tasks number of incremental load
[ https://issues.apache.org/jira/browse/HBASE-19226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248779#comment-16248779 ] Yun Zhao commented on HBASE-19226: -- Thanks for your review [~reidchan] The buckets used to record the number of regions for each partition. When offset is equal to the first bucket number, use the current startKey as a splitkey and start counting the next bucket. Ignores the startkey of the first bucket, replacing sorted.remove(sorted.first()); > Limit the reduce tasks number of incremental load > - > > Key: HBASE-19226 > URL: https://issues.apache.org/jira/browse/HBASE-19226 > Project: HBase > Issue Type: Improvement >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Minor > Attachments: HBASE-19226.master.001.patch, > HBASE-19226.master.002.patch > > > When using MapReduce job to perform an incremental load into a table,the > number of reduce tasks is the current number of regions. If there are too > many regions, will lead to network+disk I/O is too large, affecting the > real-time request. > Need to use a configuration to set a number or ratio? > Limit running reduce tasks since > [https://issues.apache.org/jira/browse/MAPREDUCE-5583], the old version can > only be set reduce number. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19226) Limit the reduce tasks number of incremental load
[ https://issues.apache.org/jira/browse/HBASE-19226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Zhao updated HBASE-19226: - Release Note: Add a configuration item `hbase.mapreduce.hfileoutputformat.reduces.ratio`, it is used to adjust the reduce tasks number for the MapReduce job when incremental load into a table，which is the ratio of the regions number between 0 and 1. > Limit the reduce tasks number of incremental load > - > > Key: HBASE-19226 > URL: https://issues.apache.org/jira/browse/HBASE-19226 > Project: HBase > Issue Type: Improvement >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Minor > Attachments: HBASE-19226.master.001.patch, > HBASE-19226.master.002.patch > > > When using MapReduce job to perform an incremental load into a table,the > number of reduce tasks is the current number of regions. If there are too > many regions, will lead to network+disk I/O is too large, affecting the > real-time request. > Need to use a configuration to set a number or ratio? > Limit running reduce tasks since > [https://issues.apache.org/jira/browse/MAPREDUCE-5583], the old version can > only be set reduce number. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19226) Limit the reduce tasks number of incremental load
[ https://issues.apache.org/jira/browse/HBASE-19226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Zhao updated HBASE-19226: - Attachment: HBASE-19226.master.002.patch > Limit the reduce tasks number of incremental load > - > > Key: HBASE-19226 > URL: https://issues.apache.org/jira/browse/HBASE-19226 > Project: HBase > Issue Type: Improvement >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Minor > Attachments: HBASE-19226.master.001.patch, > HBASE-19226.master.002.patch > > > When using MapReduce job to perform an incremental load into a table,the > number of reduce tasks is the current number of regions. If there are too > many regions, will lead to network+disk I/O is too large, affecting the > real-time request. > Need to use a configuration to set a number or ratio? > Limit running reduce tasks since > [https://issues.apache.org/jira/browse/MAPREDUCE-5583], the old version can > only be set reduce number. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19226) Limit the reduce tasks number of incremental load
[ https://issues.apache.org/jira/browse/HBASE-19226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Zhao updated HBASE-19226: - Assignee: Yun Zhao Status: Patch Available (was: Open) > Limit the reduce tasks number of incremental load > - > > Key: HBASE-19226 > URL: https://issues.apache.org/jira/browse/HBASE-19226 > Project: HBase > Issue Type: Improvement >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Minor > Attachments: HBASE-19226.master.001.patch > > > When using MapReduce job to perform an incremental load into a table,the > number of reduce tasks is the current number of regions. If there are too > many regions, will lead to network+disk I/O is too large, affecting the > real-time request. > Need to use a configuration to set a number or ratio? > Limit running reduce tasks since > [https://issues.apache.org/jira/browse/MAPREDUCE-5583], the old version can > only be set reduce number. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19226) Limit the reduce tasks number of incremental load
[ https://issues.apache.org/jira/browse/HBASE-19226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Zhao updated HBASE-19226: - Attachment: HBASE-19226.master.001.patch > Limit the reduce tasks number of incremental load > - > > Key: HBASE-19226 > URL: https://issues.apache.org/jira/browse/HBASE-19226 > Project: HBase > Issue Type: Improvement >Reporter: Yun Zhao >Priority: Minor > Attachments: HBASE-19226.master.001.patch > > > When using MapReduce job to perform an incremental load into a table,the > number of reduce tasks is the current number of regions. If there are too > many regions, will lead to network+disk I/O is too large, affecting the > real-time request. > Need to use a configuration to set a number or ratio? > Limit running reduce tasks since > [https://issues.apache.org/jira/browse/MAPREDUCE-5583], the old version can > only be set reduce number. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19226) Limit the reduce tasks number of incremental load
[ https://issues.apache.org/jira/browse/HBASE-19226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16247306#comment-16247306 ] Yun Zhao commented on HBASE-19226: -- [~reidchan] I am going to provide a patch later :D > Limit the reduce tasks number of incremental load > - > > Key: HBASE-19226 > URL: https://issues.apache.org/jira/browse/HBASE-19226 > Project: HBase > Issue Type: Improvement >Reporter: Yun Zhao >Priority: Minor > > When using MapReduce job to perform an incremental load into a table,the > number of reduce tasks is the current number of regions. If there are too > many regions, will lead to network+disk I/O is too large, affecting the > real-time request. > Need to use a configuration to set a number or ratio? > Limit running reduce tasks since > [https://issues.apache.org/jira/browse/MAPREDUCE-5583], the old version can > only be set reduce number. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-19226) Limit the reduce tasks number of incremental load
Yun Zhao created HBASE-19226: Summary: Limit the reduce tasks number of incremental load Key: HBASE-19226 URL: https://issues.apache.org/jira/browse/HBASE-19226 Project: HBase Issue Type: Improvement Reporter: Yun Zhao Priority: Minor When using MapReduce job to perform an incremental load into a table,the number of reduce tasks is the current number of regions. If there are too many regions, will lead to network+disk I/O is too large, affecting the real-time request. Need to use a configuration to set a number or ratio? Limit running reduce tasks since [https://issues.apache.org/jira/browse/MAPREDUCE-5583], the old version can only be set reduce number. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19051) Add new split algorithm for num string
[
https://issues.apache.org/jira/browse/HBASE-19051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213673#comment-16213673
]
Yun Zhao commented on HBASE-19051:
--
I have added a release note that is not necessarily accurate. You can modify
it, Thanks～. [~mdrob]
> Add new split algorithm for num string
> --
>
> Key: HBASE-19051
> URL: https://issues.apache.org/jira/browse/HBASE-19051
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-19051.branch-1.001.patch,
> HBASE-19051.master.001.patch, HBASE-19051.master.002.patch
>
>
> We will use the reversed sequential number or phone number as the first part
> of rowkey, there is no split algorithm to create a pre-split table, only by
> specify the split points.
> {code}
> create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19051) Add new split algorithm for num string
[
https://issues.apache.org/jira/browse/HBASE-19051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-19051:
-
Release Note:
Add new split algorithm DecimalStringSplit，row are decimal-encoded long values
in the range "" => "" .
create 't1','f', { NUMREGIONS => 10 , SPLITALGO => 'DecimalStringSplit' }
The split point will be 1000,2000,...,9000
was:
Add new split algorithm DecimalStringSplit，row are decimal-encoded long values
in the range "" => "" .
{code}
create 't1','f', { NUMREGIONS => 10 , SPLITALGO => 'DecimalStringSplit' }
{code}
The split point will be 1000,2000,...,9000
> Add new split algorithm for num string
> --
>
> Key: HBASE-19051
> URL: https://issues.apache.org/jira/browse/HBASE-19051
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-19051.branch-1.001.patch,
> HBASE-19051.master.001.patch, HBASE-19051.master.002.patch
>
>
> We will use the reversed sequential number or phone number as the first part
> of rowkey, there is no split algorithm to create a pre-split table, only by
> specify the split points.
> {code}
> create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19051) Add new split algorithm for num string
[
https://issues.apache.org/jira/browse/HBASE-19051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-19051:
-
Release Note:
Add new split algorithm DecimalStringSplit，row are decimal-encoded long values
in the range "" => "" .
{code}
create 't1','f', { NUMREGIONS => 10 , SPLITALGO => 'DecimalStringSplit' }
{code}
The split point will be 1000,2000,...,9000
Description:
We will use the reversed sequential number or phone number as the first part of
rowkey, there is no split algorithm to create a pre-split table, only by
specify the split points.
{code}
create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
{code}
was:
We will use the reversed sequential number or phone number as the first part of
rowkey, there is no split algorithm to create a pre-split table, only by
specify the split points.
{code}
create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
{code}
Add new split algorithm DecimalStringSplit.
{code}
create 't2','f', { NUMREGIONS => 10 , SPLITALGO => 'DecimalStringSplit' }
{code}
> Add new split algorithm for num string
> --
>
> Key: HBASE-19051
> URL: https://issues.apache.org/jira/browse/HBASE-19051
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-19051.branch-1.001.patch,
> HBASE-19051.master.001.patch, HBASE-19051.master.002.patch
>
>
> We will use the reversed sequential number or phone number as the first part
> of rowkey, there is no split algorithm to create a pre-split table, only by
> specify the split points.
> {code}
> create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19051) Add new split algorithm for num string
[
https://issues.apache.org/jira/browse/HBASE-19051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-19051:
-
Attachment: HBASE-19051.branch-1.001.patch
[~yuzhih...@gmail.com] - I just uploaded a patch for branch-1 :D
> Add new split algorithm for num string
> --
>
> Key: HBASE-19051
> URL: https://issues.apache.org/jira/browse/HBASE-19051
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-19051.branch-1.001.patch,
> HBASE-19051.master.001.patch, HBASE-19051.master.002.patch
>
>
> We will use the reversed sequential number or phone number as the first part
> of rowkey, there is no split algorithm to create a pre-split table, only by
> specify the split points.
> {code}
> create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
> {code}
> Add new split algorithm DecimalStringSplit.
> {code}
> create 't2','f', { NUMREGIONS => 10 , SPLITALGO => 'DecimalStringSplit' }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19051) Add new split algorithm for num string
[
https://issues.apache.org/jira/browse/HBASE-19051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-19051:
-
Description:
We will use the reversed sequential number or phone number as the first part of
rowkey, there is no split algorithm to create a pre-split table, only by
specify the split points.
{code}
create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
{code}
Add new split algorithm DecimalStringSplit.
{code}
create 't2','f', { NUMREGIONS => 10 , SPLITALGO => 'DecimalStringSplit' }
{code}
was:
We will use the reversed sequential number or phone number as the first part of
rowkey, there is no split algorithm to create a pre-split table, only by
specify the split points.
{code}
create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
{code}
Add new split algorithm DecStringSplit.
{code}
create 't2','f', { NUMREGIONS => 10 , SPLITALGO => 'DecStringSplit' }
{code}
> Add new split algorithm for num string
> --
>
> Key: HBASE-19051
> URL: https://issues.apache.org/jira/browse/HBASE-19051
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Attachments: HBASE-19051.master.001.patch,
> HBASE-19051.master.002.patch
>
>
> We will use the reversed sequential number or phone number as the first part
> of rowkey, there is no split algorithm to create a pre-split table, only by
> specify the split points.
> {code}
> create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
> {code}
> Add new split algorithm DecimalStringSplit.
> {code}
> create 't2','f', { NUMREGIONS => 10 , SPLITALGO => 'DecimalStringSplit' }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (HBASE-19051) Add new split algorithm for num string
[
https://issues.apache.org/jira/browse/HBASE-19051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16211502#comment-16211502
]
Yun Zhao edited comment on HBASE-19051 at 10/19/17 6:27 PM:
[~mdrob] - [~yuzhih...@gmail.com] - Thanks,I made some changes.
was (Author: yun zhao):
[~mdrob] [~yuzhih...@gmail.com] - Thanks,I made some changes.
> Add new split algorithm for num string
> --
>
> Key: HBASE-19051
> URL: https://issues.apache.org/jira/browse/HBASE-19051
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Attachments: HBASE-19051.master.001.patch,
> HBASE-19051.master.002.patch
>
>
> We will use the reversed sequential number or phone number as the first part
> of rowkey, there is no split algorithm to create a pre-split table, only by
> specify the split points.
> {code}
> create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
> {code}
> Add new split algorithm DecStringSplit.
> {code}
> create 't2','f', { NUMREGIONS => 10 , SPLITALGO => 'DecStringSplit' }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19051) Add new split algorithm for num string
[
https://issues.apache.org/jira/browse/HBASE-19051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16211502#comment-16211502
]
Yun Zhao commented on HBASE-19051:
--
[~mdrob] [~yuzhih...@gmail.com] - Thanks,I made some changes.
> Add new split algorithm for num string
> --
>
> Key: HBASE-19051
> URL: https://issues.apache.org/jira/browse/HBASE-19051
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Attachments: HBASE-19051.master.001.patch,
> HBASE-19051.master.002.patch
>
>
> We will use the reversed sequential number or phone number as the first part
> of rowkey, there is no split algorithm to create a pre-split table, only by
> specify the split points.
> {code}
> create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
> {code}
> Add new split algorithm DecStringSplit.
> {code}
> create 't2','f', { NUMREGIONS => 10 , SPLITALGO => 'DecStringSplit' }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19051) Add new split algorithm for num string
[
https://issues.apache.org/jira/browse/HBASE-19051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-19051:
-
Attachment: HBASE-19051.master.002.patch
> Add new split algorithm for num string
> --
>
> Key: HBASE-19051
> URL: https://issues.apache.org/jira/browse/HBASE-19051
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Attachments: HBASE-19051.master.001.patch,
> HBASE-19051.master.002.patch
>
>
> We will use the reversed sequential number or phone number as the first part
> of rowkey, there is no split algorithm to create a pre-split table, only by
> specify the split points.
> {code}
> create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
> {code}
> Add new split algorithm DecStringSplit.
> {code}
> create 't2','f', { NUMREGIONS => 10 , SPLITALGO => 'DecStringSplit' }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19051) Add new split algorithm for num string
[
https://issues.apache.org/jira/browse/HBASE-19051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-19051:
-
Attachment: HBASE-19051.master.001.patch
> Add new split algorithm for num string
> --
>
> Key: HBASE-19051
> URL: https://issues.apache.org/jira/browse/HBASE-19051
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Priority: Minor
> Attachments: HBASE-19051.master.001.patch
>
>
> We will use the reversed sequential number or phone number as the first part
> of rowkey, there is no split algorithm to create a pre-split table, only by
> specify the split points.
> {code}
> create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
> {code}
> Add new split algorithm DecStringSplit.
> {code}
> create 't2','f', { NUMREGIONS => 10 , SPLITALGO => 'DecStringSplit' }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19051) Add new split algorithm for num string
[
https://issues.apache.org/jira/browse/HBASE-19051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-19051:
-
Assignee: Yun Zhao
Status: Patch Available (was: Open)
> Add new split algorithm for num string
> --
>
> Key: HBASE-19051
> URL: https://issues.apache.org/jira/browse/HBASE-19051
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Attachments: HBASE-19051.master.001.patch
>
>
> We will use the reversed sequential number or phone number as the first part
> of rowkey, there is no split algorithm to create a pre-split table, only by
> specify the split points.
> {code}
> create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
> {code}
> Add new split algorithm DecStringSplit.
> {code}
> create 't2','f', { NUMREGIONS => 10 , SPLITALGO => 'DecStringSplit' }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (HBASE-19051) Add new split algorithm for num string
Yun Zhao created HBASE-19051:
Summary: Add new split algorithm for num string
Key: HBASE-19051
URL: https://issues.apache.org/jira/browse/HBASE-19051
Project: HBase
Issue Type: Improvement
Reporter: Yun Zhao
Priority: Minor
We will use the reversed sequential number or phone number as the first part of
rowkey, there is no split algorithm to create a pre-split table, only by
specify the split points.
{code}
create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
{code}
Add new split algorithm DecStringSplit.
{code}
create 't2','f', { NUMREGIONS => 10 , SPLITALGO => 'DecStringSplit' }
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18662) The default values for many configuration items in the code are not consistent with hbase-default.xml
[
https://issues.apache.org/jira/browse/HBASE-18662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16162342#comment-16162342
]
Yun Zhao commented on HBASE-18662:
--
[~chia7712] - Thank you for your suggest and patch :D. I should look at the
instructions and changes before making the patch.
> The default values for many configuration items in the code are not
> consistent with hbase-default.xml
> -
>
> Key: HBASE-18662
> URL: https://issues.apache.org/jira/browse/HBASE-18662
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Fix For: 2.0.0-alpha-3
>
> Attachments: HBASE-18662.master.002.patch,
> HBASE-18662.master.003.patch
>
>
> Such as
> {code}
> hbase.ipc.server.callqueue.handler.factor
> hbase.regionserver.logroll.errors.tolerated
> hbase.regionserver.region.split.policy
> zookeeper.session.timeout
> hbase.client.retries.number
> hbase.client.max.perserver.tasks
> hbase.client.keyvalue.maxsize
> hbase.normalizer.period
> hbase.hstore.blockingStoreFiles
> hbase.snapshot.restore.take.failsafe.snapshot
> hbase.lease.recovery.dfs.timeout
> hbase.rest.filter.classes
> hbase.http.max.threads
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18662) The default values for many configuration items in the code are not consistent with hbase-default.xml
[
https://issues.apache.org/jira/browse/HBASE-18662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-18662:
-
Attachment: (was: HBASE-18662.master.001.patch)
> The default values for many configuration items in the code are not
> consistent with hbase-default.xml
> -
>
> Key: HBASE-18662
> URL: https://issues.apache.org/jira/browse/HBASE-18662
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Attachments: HBASE-18662.master.002.patch
>
>
> Such as
> {code}
> hbase.ipc.server.callqueue.handler.factor
> hbase.regionserver.logroll.errors.tolerated
> hbase.regionserver.region.split.policy
> zookeeper.session.timeout
> hbase.client.retries.number
> hbase.client.max.perserver.tasks
> hbase.client.keyvalue.maxsize
> hbase.normalizer.period
> hbase.hstore.blockingStoreFiles
> hbase.snapshot.restore.take.failsafe.snapshot
> hbase.lease.recovery.dfs.timeout
> hbase.rest.filter.classes
> hbase.http.max.threads
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18662) The default values for many configuration items in the code are not consistent with hbase-default.xml
[
https://issues.apache.org/jira/browse/HBASE-18662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-18662:
-
Attachment: HBASE-18662.master.002.patch
> The default values for many configuration items in the code are not
> consistent with hbase-default.xml
> -
>
> Key: HBASE-18662
> URL: https://issues.apache.org/jira/browse/HBASE-18662
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Attachments: HBASE-18662.master.002.patch
>
>
> Such as
> {code}
> hbase.ipc.server.callqueue.handler.factor
> hbase.regionserver.logroll.errors.tolerated
> hbase.regionserver.region.split.policy
> zookeeper.session.timeout
> hbase.client.retries.number
> hbase.client.max.perserver.tasks
> hbase.client.keyvalue.maxsize
> hbase.normalizer.period
> hbase.hstore.blockingStoreFiles
> hbase.snapshot.restore.take.failsafe.snapshot
> hbase.lease.recovery.dfs.timeout
> hbase.rest.filter.classes
> hbase.http.max.threads
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18662) The default values for many configuration items in the code are not consistent with hbase-default.xml
[
https://issues.apache.org/jira/browse/HBASE-18662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-18662:
-
Status: Patch Available (was: Open)
> The default values for many configuration items in the code are not
> consistent with hbase-default.xml
> -
>
> Key: HBASE-18662
> URL: https://issues.apache.org/jira/browse/HBASE-18662
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Attachments: HBASE-18662.master.001.patch
>
>
> Such as
> {code}
> hbase.ipc.server.callqueue.handler.factor
> hbase.regionserver.logroll.errors.tolerated
> hbase.regionserver.region.split.policy
> zookeeper.session.timeout
> hbase.client.retries.number
> hbase.client.max.perserver.tasks
> hbase.client.keyvalue.maxsize
> hbase.normalizer.period
> hbase.hstore.blockingStoreFiles
> hbase.snapshot.restore.take.failsafe.snapshot
> hbase.lease.recovery.dfs.timeout
> hbase.rest.filter.classes
> hbase.http.max.threads
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18662) The default values for many configuration items in the code are not consistent with hbase-default.xml
[
https://issues.apache.org/jira/browse/HBASE-18662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-18662:
-
Attachment: HBASE-18662.master.001.patch
> The default values for many configuration items in the code are not
> consistent with hbase-default.xml
> -
>
> Key: HBASE-18662
> URL: https://issues.apache.org/jira/browse/HBASE-18662
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Attachments: HBASE-18662.master.001.patch
>
>
> Such as
> {code}
> hbase.ipc.server.callqueue.handler.factor
> hbase.regionserver.logroll.errors.tolerated
> hbase.regionserver.region.split.policy
> zookeeper.session.timeout
> hbase.client.retries.number
> hbase.client.max.perserver.tasks
> hbase.client.keyvalue.maxsize
> hbase.normalizer.period
> hbase.hstore.blockingStoreFiles
> hbase.snapshot.restore.take.failsafe.snapshot
> hbase.lease.recovery.dfs.timeout
> hbase.rest.filter.classes
> hbase.http.max.threads
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (HBASE-18662) The default values for many configuration items in the code are not consistent with hbase-default.xml
[
https://issues.apache.org/jira/browse/HBASE-18662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao reassigned HBASE-18662:
Assignee: Yun Zhao
> The default values for many configuration items in the code are not
> consistent with hbase-default.xml
> -
>
> Key: HBASE-18662
> URL: https://issues.apache.org/jira/browse/HBASE-18662
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Attachments: HBASE-18662.master.001.patch
>
>
> Such as
> {code}
> hbase.ipc.server.callqueue.handler.factor
> hbase.regionserver.logroll.errors.tolerated
> hbase.regionserver.region.split.policy
> zookeeper.session.timeout
> hbase.client.retries.number
> hbase.client.max.perserver.tasks
> hbase.client.keyvalue.maxsize
> hbase.normalizer.period
> hbase.hstore.blockingStoreFiles
> hbase.snapshot.restore.take.failsafe.snapshot
> hbase.lease.recovery.dfs.timeout
> hbase.rest.filter.classes
> hbase.http.max.threads
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (HBASE-18662) The default values for many configuration items in the code are not consistent with hbase-default.xml
[
https://issues.apache.org/jira/browse/HBASE-18662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137963#comment-16137963
]
Yun Zhao edited comment on HBASE-18662 at 8/23/17 9:46 AM:
---
[~st...@apache.org] Need to keep the same as hbase-default.xml?
was (Author: yun zhao):
[~st...@duboce.net] Need to keep the same as hbase-default.xml?
> The default values for many configuration items in the code are not
> consistent with hbase-default.xml
> -
>
> Key: HBASE-18662
> URL: https://issues.apache.org/jira/browse/HBASE-18662
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Priority: Minor
>
> Such as
> {code}
> hbase.ipc.server.callqueue.handler.factor
> hbase.regionserver.logroll.errors.tolerated
> hbase.regionserver.region.split.policy
> zookeeper.session.timeout
> hbase.client.retries.number
> hbase.client.max.perserver.tasks
> hbase.client.keyvalue.maxsize
> hbase.normalizer.period
> hbase.hstore.blockingStoreFiles
> hbase.snapshot.restore.take.failsafe.snapshot
> hbase.lease.recovery.dfs.timeout
> hbase.rest.filter.classes
> hbase.http.max.threads
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (HBASE-18662) The default values for many configuration items in the code are not consistent with hbase-default.xml
Yun Zhao created HBASE-18662:
Summary: The default values for many configuration items in the
code are not consistent with hbase-default.xml
Key: HBASE-18662
URL: https://issues.apache.org/jira/browse/HBASE-18662
Project: HBase
Issue Type: Improvement
Reporter: Yun Zhao
Priority: Minor
Such as
{code}
hbase.ipc.server.callqueue.handler.factor
hbase.regionserver.logroll.errors.tolerated
hbase.regionserver.region.split.policy
zookeeper.session.timeout
hbase.client.retries.number
hbase.client.max.perserver.tasks
hbase.client.keyvalue.maxsize
hbase.normalizer.period
hbase.hstore.blockingStoreFiles
hbase.snapshot.restore.take.failsafe.snapshot
hbase.lease.recovery.dfs.timeout
hbase.rest.filter.classes
hbase.http.max.threads
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18662) The default values for many configuration items in the code are not consistent with hbase-default.xml
[
https://issues.apache.org/jira/browse/HBASE-18662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137963#comment-16137963
]
Yun Zhao commented on HBASE-18662:
--
[~st...@duboce.net] Need to keep the same as hbase-default.xml?
> The default values for many configuration items in the code are not
> consistent with hbase-default.xml
> -
>
> Key: HBASE-18662
> URL: https://issues.apache.org/jira/browse/HBASE-18662
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Priority: Minor
>
> Such as
> {code}
> hbase.ipc.server.callqueue.handler.factor
> hbase.regionserver.logroll.errors.tolerated
> hbase.regionserver.region.split.policy
> zookeeper.session.timeout
> hbase.client.retries.number
> hbase.client.max.perserver.tasks
> hbase.client.keyvalue.maxsize
> hbase.normalizer.period
> hbase.hstore.blockingStoreFiles
> hbase.snapshot.restore.take.failsafe.snapshot
> hbase.lease.recovery.dfs.timeout
> hbase.rest.filter.classes
> hbase.http.max.threads
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (HBASE-18660) Remove duplicate code from the checkAndPut method in HTable
[ https://issues.apache.org/jira/browse/HBASE-18660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Zhao reassigned HBASE-18660: Assignee: Yun Zhao > Remove duplicate code from the checkAndPut method in HTable > --- > > Key: HBASE-18660 > URL: https://issues.apache.org/jira/browse/HBASE-18660 > Project: HBase > Issue Type: Task >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Trivial > Attachments: HBASE-18660.master.001.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18660) Remove duplicate code from the checkAndPut method in HTable
[ https://issues.apache.org/jira/browse/HBASE-18660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Zhao updated HBASE-18660: - Status: Patch Available (was: Open) Simple code refactoring > Remove duplicate code from the checkAndPut method in HTable > --- > > Key: HBASE-18660 > URL: https://issues.apache.org/jira/browse/HBASE-18660 > Project: HBase > Issue Type: Task >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Trivial > Attachments: HBASE-18660.master.001.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18660) Remove duplicate code from the checkAndPut method in HTable
[ https://issues.apache.org/jira/browse/HBASE-18660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Zhao updated HBASE-18660: - Attachment: HBASE-18660.master.001.patch > Remove duplicate code from the checkAndPut method in HTable > --- > > Key: HBASE-18660 > URL: https://issues.apache.org/jira/browse/HBASE-18660 > Project: HBase > Issue Type: Task >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Trivial > Attachments: HBASE-18660.master.001.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18660) Remove duplicate code from the checkAndPut method in HTable
Yun Zhao created HBASE-18660: Summary: Remove duplicate code from the checkAndPut method in HTable Key: HBASE-18660 URL: https://issues.apache.org/jira/browse/HBASE-18660 Project: HBase Issue Type: Task Reporter: Yun Zhao Priority: Trivial -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18529) Do not delete the tmp jars dir when load the coprocessor jar
[
https://issues.apache.org/jira/browse/HBASE-18529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118005#comment-16118005
]
Yun Zhao commented on HBASE-18529:
--
[~gsbiju] - We can isolate multiple RSes by different hbase.local.dir.
Do you mean by default is different, such as using hbase.local.dir +
ServerName? I think it will add too much dir.
> Do not delete the tmp jars dir when load the coprocessor jar
>
>
> Key: HBASE-18529
> URL: https://issues.apache.org/jira/browse/HBASE-18529
> Project: HBase
> Issue Type: Bug
> Components: Coprocessors
>Reporter: Yun Zhao
>Assignee: Yun Zhao
> Attachments: HBASE-18529.master.001.patch,
> HBASE-18529.master.002.patch
>
>
> When multi regionserver is deployed on a single server, used default
> hbase.local.dir . The tmp jars dir will deleted when one of them is restarted.
> Also when multi regionserver start at the same time, the jar in the
> copyToLocalFile process may be deleted, causing the coprocessor load failed.
> {code}
> 2017-08-06 20:02:15,326 ERROR [RS_OPEN_REGION--2]
> regionserver.RegionCoprocessorHost: Failed to load coprocessor
> ENOENT: No such file or directory
> at org.apache.hadoop.io.nativeio.NativeIO$POSIX.chmodImpl(Native
> Method)
> at
> org.apache.hadoop.io.nativeio.NativeIO$POSIX.chmod(NativeIO.java:226)
> at
> org.apache.hadoop.fs.RawLocalFileSystem.setPermission(RawLocalFileSystem.java:629)
> at
> org.apache.hadoop.fs.FilterFileSystem.setPermission(FilterFileSystem.java:467)
> at
> org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:456)
> at
> org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:424)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:906)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:887)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:784)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:365)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:338)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:289)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1968)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1937)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1913)
> at
> org.apache.hadoop.hbase.util.CoprocessorClassLoader.init(CoprocessorClassLoader.java:168)
> at
> org.apache.hadoop.hbase.util.CoprocessorClassLoader.getClassLoader(CoprocessorClassLoader.java:250)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18529) Do not delete the tmp jars dir when load the coprocessor jar
[
https://issues.apache.org/jira/browse/HBASE-18529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-18529:
-
Attachment: HBASE-18529.master.002.patch
> Do not delete the tmp jars dir when load the coprocessor jar
>
>
> Key: HBASE-18529
> URL: https://issues.apache.org/jira/browse/HBASE-18529
> Project: HBase
> Issue Type: Bug
> Components: Coprocessors
>Reporter: Yun Zhao
>Assignee: Yun Zhao
> Attachments: HBASE-18529.master.001.patch,
> HBASE-18529.master.002.patch
>
>
> When multi regionserver is deployed on a single server, used default
> hbase.local.dir . The tmp jars dir will deleted when one of them is restarted.
> Also when multi regionserver start at the same time, the jar in the
> copyToLocalFile process may be deleted, causing the coprocessor load failed.
> {code}
> 2017-08-06 20:02:15,326 ERROR [RS_OPEN_REGION--2]
> regionserver.RegionCoprocessorHost: Failed to load coprocessor
> ENOENT: No such file or directory
> at org.apache.hadoop.io.nativeio.NativeIO$POSIX.chmodImpl(Native
> Method)
> at
> org.apache.hadoop.io.nativeio.NativeIO$POSIX.chmod(NativeIO.java:226)
> at
> org.apache.hadoop.fs.RawLocalFileSystem.setPermission(RawLocalFileSystem.java:629)
> at
> org.apache.hadoop.fs.FilterFileSystem.setPermission(FilterFileSystem.java:467)
> at
> org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:456)
> at
> org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:424)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:906)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:887)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:784)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:365)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:338)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:289)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1968)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1937)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1913)
> at
> org.apache.hadoop.hbase.util.CoprocessorClassLoader.init(CoprocessorClassLoader.java:168)
> at
> org.apache.hadoop.hbase.util.CoprocessorClassLoader.getClassLoader(CoprocessorClassLoader.java:250)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18529) Do not delete the tmp jars dir when load the coprocessor jar
[
https://issues.apache.org/jira/browse/HBASE-18529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116638#comment-16116638
]
Yun Zhao commented on HBASE-18529:
--
[~tedyu] If do not need to remove the old jar, can i remove this test case?
Actually the old jar will removed at jvm normal stop. #deleteOnExit
> Do not delete the tmp jars dir when load the coprocessor jar
>
>
> Key: HBASE-18529
> URL: https://issues.apache.org/jira/browse/HBASE-18529
> Project: HBase
> Issue Type: Bug
> Components: Coprocessors
>Reporter: Yun Zhao
>Assignee: Yun Zhao
> Attachments: HBASE-18529.master.001.patch
>
>
> When multi regionserver is deployed on a single server, used default
> hbase.local.dir . The tmp jars dir will deleted when one of them is restarted.
> Also when multi regionserver start at the same time, the jar in the
> copyToLocalFile process may be deleted, causing the coprocessor load failed.
> {code}
> 2017-08-06 20:02:15,326 ERROR [RS_OPEN_REGION--2]
> regionserver.RegionCoprocessorHost: Failed to load coprocessor
> ENOENT: No such file or directory
> at org.apache.hadoop.io.nativeio.NativeIO$POSIX.chmodImpl(Native
> Method)
> at
> org.apache.hadoop.io.nativeio.NativeIO$POSIX.chmod(NativeIO.java:226)
> at
> org.apache.hadoop.fs.RawLocalFileSystem.setPermission(RawLocalFileSystem.java:629)
> at
> org.apache.hadoop.fs.FilterFileSystem.setPermission(FilterFileSystem.java:467)
> at
> org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:456)
> at
> org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:424)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:906)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:887)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:784)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:365)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:338)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:289)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1968)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1937)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1913)
> at
> org.apache.hadoop.hbase.util.CoprocessorClassLoader.init(CoprocessorClassLoader.java:168)
> at
> org.apache.hadoop.hbase.util.CoprocessorClassLoader.getClassLoader(CoprocessorClassLoader.java:250)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18529) Do not delete the tmp jars dir when load the coprocessor jar
[
https://issues.apache.org/jira/browse/HBASE-18529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-18529:
-
Component/s: Coprocessors
> Do not delete the tmp jars dir when load the coprocessor jar
>
>
> Key: HBASE-18529
> URL: https://issues.apache.org/jira/browse/HBASE-18529
> Project: HBase
> Issue Type: Bug
> Components: Coprocessors
>Reporter: Yun Zhao
>Assignee: Yun Zhao
> Attachments: HBASE-18529.master.001.patch
>
>
> When multi regionserver is deployed on a single server, used default
> hbase.local.dir . The tmp jars dir will deleted when one of them is restarted.
> Also when multi regionserver start at the same time, the jar in the
> copyToLocalFile process may be deleted, causing the coprocessor load failed.
> {code}
> 2017-08-06 20:02:15,326 ERROR [RS_OPEN_REGION--2]
> regionserver.RegionCoprocessorHost: Failed to load coprocessor
> ENOENT: No such file or directory
> at org.apache.hadoop.io.nativeio.NativeIO$POSIX.chmodImpl(Native
> Method)
> at
> org.apache.hadoop.io.nativeio.NativeIO$POSIX.chmod(NativeIO.java:226)
> at
> org.apache.hadoop.fs.RawLocalFileSystem.setPermission(RawLocalFileSystem.java:629)
> at
> org.apache.hadoop.fs.FilterFileSystem.setPermission(FilterFileSystem.java:467)
> at
> org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:456)
> at
> org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:424)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:906)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:887)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:784)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:365)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:338)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:289)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1968)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1937)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1913)
> at
> org.apache.hadoop.hbase.util.CoprocessorClassLoader.init(CoprocessorClassLoader.java:168)
> at
> org.apache.hadoop.hbase.util.CoprocessorClassLoader.getClassLoader(CoprocessorClassLoader.java:250)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (HBASE-18436) Add client-side hedged read metrics
[ https://issues.apache.org/jira/browse/HBASE-18436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Zhao reassigned HBASE-18436: Assignee: (was: Yun Zhao) > Add client-side hedged read metrics > --- > > Key: HBASE-18436 > URL: https://issues.apache.org/jira/browse/HBASE-18436 > Project: HBase > Issue Type: Improvement >Reporter: Yun Zhao >Priority: Minor > Attachments: HBASE-18436.master.001.patch > > > Need some metrics to represent indicate read high-availability. > +hedgedReadOps -- the number of hedged read that have occurred. > +hedgedReadWin -- the number of hedged read returned faster than the original > read. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18529) Do not delete the tmp jars dir when load the coprocessor jar
[
https://issues.apache.org/jira/browse/HBASE-18529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-18529:
-
Status: Patch Available (was: Open)
> Do not delete the tmp jars dir when load the coprocessor jar
>
>
> Key: HBASE-18529
> URL: https://issues.apache.org/jira/browse/HBASE-18529
> Project: HBase
> Issue Type: Bug
>Reporter: Yun Zhao
>Assignee: Yun Zhao
> Attachments: HBASE-18529.master.001.patch
>
>
> When multi regionserver is deployed on a single server, used default
> hbase.local.dir . The tmp jars dir will deleted when one of them is restarted.
> Also when multi regionserver start at the same time, the jar in the
> copyToLocalFile process may be deleted, causing the coprocessor load failed.
> {code}
> 2017-08-06 20:02:15,326 ERROR [RS_OPEN_REGION--2]
> regionserver.RegionCoprocessorHost: Failed to load coprocessor
> ENOENT: No such file or directory
> at org.apache.hadoop.io.nativeio.NativeIO$POSIX.chmodImpl(Native
> Method)
> at
> org.apache.hadoop.io.nativeio.NativeIO$POSIX.chmod(NativeIO.java:226)
> at
> org.apache.hadoop.fs.RawLocalFileSystem.setPermission(RawLocalFileSystem.java:629)
> at
> org.apache.hadoop.fs.FilterFileSystem.setPermission(FilterFileSystem.java:467)
> at
> org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:456)
> at
> org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:424)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:906)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:887)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:784)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:365)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:338)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:289)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1968)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1937)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1913)
> at
> org.apache.hadoop.hbase.util.CoprocessorClassLoader.init(CoprocessorClassLoader.java:168)
> at
> org.apache.hadoop.hbase.util.CoprocessorClassLoader.getClassLoader(CoprocessorClassLoader.java:250)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (HBASE-18529) Do not delete the tmp jars dir when load the coprocessor jar
[
https://issues.apache.org/jira/browse/HBASE-18529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao reassigned HBASE-18529:
Assignee: Yun Zhao
> Do not delete the tmp jars dir when load the coprocessor jar
>
>
> Key: HBASE-18529
> URL: https://issues.apache.org/jira/browse/HBASE-18529
> Project: HBase
> Issue Type: Bug
>Reporter: Yun Zhao
>Assignee: Yun Zhao
> Attachments: HBASE-18529.master.001.patch
>
>
> When multi regionserver is deployed on a single server, used default
> hbase.local.dir . The tmp jars dir will deleted when one of them is restarted.
> Also when multi regionserver start at the same time, the jar in the
> copyToLocalFile process may be deleted, causing the coprocessor load failed.
> {code}
> 2017-08-06 20:02:15,326 ERROR [RS_OPEN_REGION--2]
> regionserver.RegionCoprocessorHost: Failed to load coprocessor
> ENOENT: No such file or directory
> at org.apache.hadoop.io.nativeio.NativeIO$POSIX.chmodImpl(Native
> Method)
> at
> org.apache.hadoop.io.nativeio.NativeIO$POSIX.chmod(NativeIO.java:226)
> at
> org.apache.hadoop.fs.RawLocalFileSystem.setPermission(RawLocalFileSystem.java:629)
> at
> org.apache.hadoop.fs.FilterFileSystem.setPermission(FilterFileSystem.java:467)
> at
> org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:456)
> at
> org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:424)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:906)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:887)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:784)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:365)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:338)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:289)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1968)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1937)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1913)
> at
> org.apache.hadoop.hbase.util.CoprocessorClassLoader.init(CoprocessorClassLoader.java:168)
> at
> org.apache.hadoop.hbase.util.CoprocessorClassLoader.getClassLoader(CoprocessorClassLoader.java:250)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18529) Do not delete the tmp jars dir when load the coprocessor jar
[
https://issues.apache.org/jira/browse/HBASE-18529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-18529:
-
Attachment: HBASE-18529.master.001.patch
> Do not delete the tmp jars dir when load the coprocessor jar
>
>
> Key: HBASE-18529
> URL: https://issues.apache.org/jira/browse/HBASE-18529
> Project: HBase
> Issue Type: Bug
>Reporter: Yun Zhao
> Attachments: HBASE-18529.master.001.patch
>
>
> When multi regionserver is deployed on a single server, used default
> hbase.local.dir . The tmp jars dir will deleted when one of them is restarted.
> Also when multi regionserver start at the same time, the jar in the
> copyToLocalFile process may be deleted, causing the coprocessor load failed.
> {code}
> 2017-08-06 20:02:15,326 ERROR [RS_OPEN_REGION--2]
> regionserver.RegionCoprocessorHost: Failed to load coprocessor
> ENOENT: No such file or directory
> at org.apache.hadoop.io.nativeio.NativeIO$POSIX.chmodImpl(Native
> Method)
> at
> org.apache.hadoop.io.nativeio.NativeIO$POSIX.chmod(NativeIO.java:226)
> at
> org.apache.hadoop.fs.RawLocalFileSystem.setPermission(RawLocalFileSystem.java:629)
> at
> org.apache.hadoop.fs.FilterFileSystem.setPermission(FilterFileSystem.java:467)
> at
> org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:456)
> at
> org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:424)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:906)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:887)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:784)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:365)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:338)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:289)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1968)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1937)
> at
> org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1913)
> at
> org.apache.hadoop.hbase.util.CoprocessorClassLoader.init(CoprocessorClassLoader.java:168)
> at
> org.apache.hadoop.hbase.util.CoprocessorClassLoader.getClassLoader(CoprocessorClassLoader.java:250)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (HBASE-18529) Do not delete the tmp jars dir when load the coprocessor jar
Yun Zhao created HBASE-18529:
Summary: Do not delete the tmp jars dir when load the coprocessor
jar
Key: HBASE-18529
URL: https://issues.apache.org/jira/browse/HBASE-18529
Project: HBase
Issue Type: Bug
Reporter: Yun Zhao
When multi regionserver is deployed on a single server, used default
hbase.local.dir . The tmp jars dir will deleted when one of them is restarted.
Also when multi regionserver start at the same time, the jar in the
copyToLocalFile process may be deleted, causing the coprocessor load failed.
{code}
2017-08-06 20:02:15,326 ERROR [RS_OPEN_REGION--2]
regionserver.RegionCoprocessorHost: Failed to load coprocessor
ENOENT: No such file or directory
at org.apache.hadoop.io.nativeio.NativeIO$POSIX.chmodImpl(Native Method)
at org.apache.hadoop.io.nativeio.NativeIO$POSIX.chmod(NativeIO.java:226)
at
org.apache.hadoop.fs.RawLocalFileSystem.setPermission(RawLocalFileSystem.java:629)
at
org.apache.hadoop.fs.FilterFileSystem.setPermission(FilterFileSystem.java:467)
at
org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:456)
at
org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:424)
at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:906)
at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:887)
at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:784)
at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:365)
at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:338)
at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:289)
at org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1968)
at org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1937)
at org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1913)
at
org.apache.hadoop.hbase.util.CoprocessorClassLoader.init(CoprocessorClassLoader.java:168)
at
org.apache.hadoop.hbase.util.CoprocessorClassLoader.getClassLoader(CoprocessorClassLoader.java:250)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18436) Add client-side hedged read metrics
[ https://issues.apache.org/jira/browse/HBASE-18436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Zhao updated HBASE-18436: - Status: Open (was: Patch Available) > Add client-side hedged read metrics > --- > > Key: HBASE-18436 > URL: https://issues.apache.org/jira/browse/HBASE-18436 > Project: HBase > Issue Type: Improvement >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Minor > Attachments: HBASE-18436.master.001.patch > > > Need some metrics to represent indicate read high-availability. > +hedgedReadOps -- the number of hedged read that have occurred. > +hedgedReadWin -- the number of hedged read returned faster than the original > read. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18436) Add client-side hedged read metrics
[ https://issues.apache.org/jira/browse/HBASE-18436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16097894#comment-16097894 ] Yun Zhao commented on HBASE-18436: -- I'll add some metrics for ScannerCallableWithReplicas later. > Add client-side hedged read metrics > --- > > Key: HBASE-18436 > URL: https://issues.apache.org/jira/browse/HBASE-18436 > Project: HBase > Issue Type: Improvement >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Minor > Attachments: HBASE-18436.master.001.patch > > > Need some metrics to represent indicate read high-availability. > +hedgedReadOps -- the number of hedged read that have occurred. > +hedgedReadWin -- the number of hedged read returned faster than the original > read. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18436) Add client-side hedged read metrics
[ https://issues.apache.org/jira/browse/HBASE-18436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Zhao updated HBASE-18436: - Assignee: Yun Zhao Status: Patch Available (was: Open) > Add client-side hedged read metrics > --- > > Key: HBASE-18436 > URL: https://issues.apache.org/jira/browse/HBASE-18436 > Project: HBase > Issue Type: Improvement >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Minor > Attachments: HBASE-18436.master.001.patch > > > Need some metrics to represent indicate read high-availability. > +hedgedReadOps -- the number of hedged read that have occurred. > +hedgedReadWin -- the number of hedged read returned faster than the original > read. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18436) Add client-side hedged read metrics
[ https://issues.apache.org/jira/browse/HBASE-18436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Zhao updated HBASE-18436: - Attachment: HBASE-18436.master.001.patch > Add client-side hedged read metrics > --- > > Key: HBASE-18436 > URL: https://issues.apache.org/jira/browse/HBASE-18436 > Project: HBase > Issue Type: Improvement >Reporter: Yun Zhao >Priority: Minor > Attachments: HBASE-18436.master.001.patch > > > Need some metrics to represent indicate read high-availability. > +hedgedReadOps -- the number of hedged read that have occurred. > +hedgedReadWin -- the number of hedged read returned faster than the original > read. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18436) Add client-side hedged read metrics
Yun Zhao created HBASE-18436: Summary: Add client-side hedged read metrics Key: HBASE-18436 URL: https://issues.apache.org/jira/browse/HBASE-18436 Project: HBase Issue Type: Improvement Reporter: Yun Zhao Priority: Minor Need some metrics to represent indicate read high-availability. +hedgedReadOps -- the number of hedged read that have occurred. +hedgedReadWin -- the number of hedged read returned faster than the original read. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18412) [Shell] Support unset of a list of table configuration
[ https://issues.apache.org/jira/browse/HBASE-18412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16092688#comment-16092688 ] Yun Zhao commented on HBASE-18412: -- I did not support column family:( > [Shell] Support unset of a list of table configuration > -- > > Key: HBASE-18412 > URL: https://issues.apache.org/jira/browse/HBASE-18412 > Project: HBase > Issue Type: Improvement >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Minor > Attachments: HBASE-18412.master.001.patch > > > Add a method 'table_conf_unset' in admin.rb to reset the configuration as the > system default. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18412) [Shell] Support unset of a list of table configuration
[ https://issues.apache.org/jira/browse/HBASE-18412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Zhao updated HBASE-18412: - Status: Patch Available (was: Open) > [Shell] Support unset of a list of table configuration > -- > > Key: HBASE-18412 > URL: https://issues.apache.org/jira/browse/HBASE-18412 > Project: HBase > Issue Type: Improvement >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Minor > Attachments: HBASE-18412.master.001.patch > > > Add a method 'table_conf_unset' in admin.rb to reset the configuration as the > system default. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18412) [Shell] Support unset of a list of table configuration
[ https://issues.apache.org/jira/browse/HBASE-18412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Zhao updated HBASE-18412: - Attachment: HBASE-18412.master.001.patch > [Shell] Support unset of a list of table configuration > -- > > Key: HBASE-18412 > URL: https://issues.apache.org/jira/browse/HBASE-18412 > Project: HBase > Issue Type: Improvement >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Minor > Attachments: HBASE-18412.master.001.patch > > > Add a method 'table_conf_unset' in admin.rb to reset the configuration as the > system default. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18412) [Shell] Support unset of a list of table configuration
Yun Zhao created HBASE-18412: Summary: [Shell] Support unset of a list of table configuration Key: HBASE-18412 URL: https://issues.apache.org/jira/browse/HBASE-18412 Project: HBase Issue Type: Improvement Reporter: Yun Zhao Assignee: Yun Zhao Priority: Minor Add a method 'table_conf_unset' in admin.rb to reset the configuration as the system default. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18403) [Shell]Truncate permission required
[ https://issues.apache.org/jira/browse/HBASE-18403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16092531#comment-16092531 ] Yun Zhao commented on HBASE-18403: -- [~mdrob] - Based on the existing ruby script, I have no way to create a non-superuser user to execute the truncate command :( . > [Shell]Truncate permission required > --- > > Key: HBASE-18403 > URL: https://issues.apache.org/jira/browse/HBASE-18403 > Project: HBase > Issue Type: Improvement > Components: shell >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Trivial > Attachments: HBASE-18403.patch > > > When a user has only (Create) permission to execute truncate, the table will > be deleted and not re-created -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18403) [Shell]Truncate permission required
[ https://issues.apache.org/jira/browse/HBASE-18403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16092446#comment-16092446 ] Yun Zhao commented on HBASE-18403: -- [~syuanjiang]Not java code, is admin.rb bug,because org.apache.hadoop.hbase.security.AccessDeniedException is a subclass of org.apache.hadoop.hbase.DoNotRetryIOException。 > [Shell]Truncate permission required > --- > > Key: HBASE-18403 > URL: https://issues.apache.org/jira/browse/HBASE-18403 > Project: HBase > Issue Type: Improvement > Components: shell >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Trivial > Attachments: HBASE-18403.patch > > > When a user has only (Create) permission to execute truncate, the table will > be deleted and not re-created -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18403) [Shell]Truncate permission required
[ https://issues.apache.org/jira/browse/HBASE-18403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16092444#comment-16092444 ] Yun Zhao commented on HBASE-18403: -- [~mdrob] tks,I try to add a test. > [Shell]Truncate permission required > --- > > Key: HBASE-18403 > URL: https://issues.apache.org/jira/browse/HBASE-18403 > Project: HBase > Issue Type: Improvement > Components: shell >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Trivial > Attachments: HBASE-18403.patch > > > When a user has only (Create) permission to execute truncate, the table will > be deleted and not re-created -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18403) [Shell]Truncate permission required
[ https://issues.apache.org/jira/browse/HBASE-18403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Zhao updated HBASE-18403: - Status: Patch Available (was: Open) > [Shell]Truncate permission required > --- > > Key: HBASE-18403 > URL: https://issues.apache.org/jira/browse/HBASE-18403 > Project: HBase > Issue Type: Improvement > Components: shell >Reporter: Yun Zhao >Priority: Trivial > Attachments: HBASE-18403.patch > > > When a user has only (Create) permission to execute truncate, the table will > be deleted and not re-created -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18403) [Shell]Truncate permission required
[ https://issues.apache.org/jira/browse/HBASE-18403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Zhao updated HBASE-18403: - Attachment: HBASE-18403.patch > [Shell]Truncate permission required > --- > > Key: HBASE-18403 > URL: https://issues.apache.org/jira/browse/HBASE-18403 > Project: HBase > Issue Type: Improvement > Components: shell >Reporter: Yun Zhao >Priority: Trivial > Attachments: HBASE-18403.patch > > > When a user has only (Create) permission to execute truncate, the table will > be deleted and not re-created -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18403) [Shell]Truncate permission required
Yun Zhao created HBASE-18403: Summary: [Shell]Truncate permission required Key: HBASE-18403 URL: https://issues.apache.org/jira/browse/HBASE-18403 Project: HBase Issue Type: Improvement Components: shell Reporter: Yun Zhao Priority: Trivial When a user has only (Create) permission to execute truncate, the table will be deleted and not re-created -- This message was sent by Atlassian JIRA (v6.4.14#64029)
