Database Reference
In-Depth Information
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.zookeeer.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
Args:
tablename Name of the table to copy
Consider the following examples.
To copy TestTable to a cluster that uses replication for a 1-hour window, use the
following command:
$ bin/hbase org.apache.hadoop.hbase.mapreduce.CopyTable
--starttime=1265875194289 --endtime=1265878794289 --peer.adr=server1,serv
er2,server3:2181:/hbase --families=myOldCf:myNewCf,cf2,cf3 TestTable
For performance, consider the following options:
-Dhbase.client.scanner.caching=100
-Dmapred.map.tasks.speculative.execution=false
Cluster monitoring
In large distributed systems, an administrator handles the dificult task of being
aware of the overall status of the system, as well as knowing about each server
separately. In disaster-like situations, it is dificult to know when and how it got
started just by looking at a handful of raw logiles.
 
Search WWH ::




Custom Search