You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2016/12/28 21:43:59 UTC
[jira] [Created] (HBASE-17385) Change usage documentation from
bin/hbase to hbase in various tools
Enis Soztutar created HBASE-17385:
-------------------------------------
Summary: Change usage documentation from bin/hbase to hbase in various tools
Key: HBASE-17385
URL: https://issues.apache.org/jira/browse/HBASE-17385
Project: HBase
Issue Type: Bug
Reporter: Enis Soztutar
Some tools print bin/hbase in their usage documentation.{{bin/hbase}} is only applicable to development environments. Typical deployments always should just refer to {{hbase}}.
For example, CopyTable usage is like:
{code}
Usage: CopyTable [general options] [--starttime=X] [--endtime=Y] [--new.name=NEW] [--peer.adr=ADR] <tablename>
Options:
rs.class hbase.regionserver.class of the peer cluster
specify if different from current cluster
rs.impl hbase.regionserver.impl of the peer cluster
startrow the start row
stoprow the stop row
starttime beginning of the time range (unixtime in millis)
without endtime means from starttime to forever
endtime end of the time range. Ignored if no starttime specified.
versions number of cell versions to copy
new.name new table's name
peer.adr Address of the peer cluster given in the format
hbase.zookeeper.quorum:hbase.zookeeper.client.port:zookeeper.znode.parent
families comma-separated list of families to copy
To copy from cf1 to cf2, give sourceCfName:destCfName.
To keep the same name, just give "cfName"
all.cells also copy delete markers and deleted cells
bulkload Write input into HFiles and bulk load to the destination table
Args:
tablename Name of the table to copy
Examples:
To copy 'TestTable' to a cluster that uses replication for a 1 hour window:
$ bin/hbase org.apache.hadoop.hbase.mapreduce.CopyTable --starttime=1265875194289 --endtime=1265878794289 --peer.adr=server1,server2,server3:2181:/hbase --families=myOldCf:myNewCf,cf2,cf3 TestTable
For performance consider the following general option:
It is recommended that you set the following to >=100. A higher value uses more memory but
decreases the round trip time to the server and may increase performance.
-Dhbase.client.scanner.caching=100
The following should always be set to false, to prevent writing data twice, which may produce
inaccurate results.
-Dmapreduce.map.speculative=false
{code}
in above, it should be:
{code}
To copy 'TestTable' to a cluster that uses replication for a 1 hour window:
$ hbase org.apache.hadoop.hbase.mapreduce.CopyTable --starttime=1265875194289 --endtime=1265878794289 --peer.adr=server1,server2,server3:2181:/hbase --
families=myOldCf:myNewCf,cf2,cf3 TestTable
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)