![]() SAP Adaptive Server Enterprise 16.0 Release Bulletin SAP Adaptive Server Enterprise 16.0 for HP-UX Release Bulletin SAP Adaptive Server Enterprise 16.0 for IBM AIX.
Apache HBase ™ Reference Guide. HBase provides several tools for administration, analysis, and debugging of your cluster. The entry- point to most of these tools is the bin/hbase command, though some tools are available in the dev- support/ directory. To see usage instructions for bin/hbase command, run it with no arguments, or with the - h argument. These are the usage instructions for HBase 0. Some commands, such as version, pe, ltt, clean, are not available in previous versions.$ bin/hbase. Usage: hbase [< options> ] < command> [< args> ]. DIR Configuration direction to use. Default: ./conf. - -hosts HOSTS Override the list in 'regionservers' file. Some commands take arguments. Pass no args or - h for usage. Run the HBase shell. Run the hbase 'fsck' tool. Write- ahead- log analyzer. Store file analyzer. Run the Zoo. Keeper shell. Upgrade hbase. master Run an HBase HMaster node. Run an HBase HRegion. Server node. zookeeper Run a Zoo. Keeper server. rest Run an HBase REST server. Run the HBase Thrift server. Run the HBase Thrift. Run the HBase clean up script. Dump hbase CLASSPATH. Dump CLASSPATH entries required by mapreduce. Run Performance. Evaluation. Run Load. Test. Tool. Print the version. CLASSNAME Run the class named CLASSNAMESome of the tools and utilities below are Java classes which are passed directly to the bin/hbase command, as referred to in the last line of the usage instructions. Others, such as hbase shell (The Apache HBase Shell), hbase upgrade (Upgrading), and hbase thrift (Thrift API and Filter Language), are documented elsewhere in this guide. Canary. There is a Canary class can help users to canary- test the HBase cluster status, with every column- family for every regions or Region. Server’s granularity. To see the usage, use the - -help parameter.$ ${HBASE_HOME}/bin/hbase canary - help. Usage: bin/hbase org. Canary [opts] [table. Show this help and exit. Continuous check at defined intervals. N> Interval between checks (sec). Use region/regionserver as regular expression. B> stop whole program if first error occurs, default is true. N> timeout for a check, default is 6. Sniffing enable the write sniffing in canary. Failure. As. Error treats read / write failure as error. Table The table used for write sniffing. Default is hbase: canary. D< config. Property> =< value> assigning or override the configuration params. This tool will return non zero error codes to user for collaborating with other monitoring tools, such as Nagios. The error code definitions are: privatestaticfinalint USAGE_EXIT_CODE = 1. INIT_ERROR_EXIT_CODE = 2. TIMEOUT_ERROR_EXIT_CODE = 3. ERROR_EXIT_CODE = 4; Here are some examples based on the following given case. There are two Table objects called test- 0. Region. Servers. see following table. Region. Servertest- 0. Following are some examples based on the previous given case. Canary test for every column family (store) of every region of every table$ ${HBASE_HOME}/bin/hbase canary. INFO tool. Canary: read from region test- 0. INFO tool. Canary: read from region test- 0. INFO tool. Canary: read from region test- 0. INFO tool. Canary: read from region test- 0. INFO tool. Canary: read from region test- 0. INFO tool. Canary: read from region test- 0. INFO tool. Canary: read from region test- 0. INFO tool. Canary: read from region test- 0. So you can see, table test- 0. Canary tool will pick 4 small piece of data from 4 (2 region * 2 store) different stores. This is a default behavior of the this tool does. Canary test for every column family (store) of every region of specific table(s)You can also test one or more specific tables.$ ${HBASE_HOME}/bin/hbase canary test- 0. Canary test with Region. Server granularity. This will pick one small piece of data from each Region. Server, and can also put your Region. Server name as input options for canary- test specific Region. Server.$ ${HBASE_HOME}/bin/hbase canary - regionserver. INFO tool. Canary: Read from table: test- 0. INFO tool. Canary: Read from table: test- 0. INFO tool. Canary: Read from table: test- 0. Canary test with regular expression pattern. This will test both table test- 0. HBASE_HOME}/bin/hbase canary - e test- 0[1- 2]1. Run canary test as daemon mode. Run repeatedly with interval defined in option - interval whose default value is 6 seconds. This daemon will stop itself and return non- zero error code if any error occurs, due to the default value of option - f is true.$ ${HBASE_HOME}/bin/hbase canary - daemon. Run repeatedly with internal 5 seconds and will not stop itself even if errors occur in the test.$ ${HBASE_HOME}/bin/hbase canary - daemon - interval 5. Force timeout if canary test stuck. In some cases the request is stuck and no response is sent back to the client. This can happen with dead Region. Servers which the master has not yet noticed. Because of this we provide a timeout option to kill the canary test and return a non- zero error code. This run sets the timeout value to 6. HBASE_HOME}/bin/hbase canary - t 6. Enable write sniffing in canary. By default, the canary tool only check the read operations, it’s hard to find the problem in the. To enable the write sniffing, you can run canary with the - write. Sniffing option. When the write sniffing is enabled, the canary tool will create an hbase table and make sure the. In each sniffing period, the canary will. HBASE_HOME}/bin/hbase canary - write. Sniffing. The default write table is hbase: canary and can be specified by the option - write. Table.$ ${HBASE_HOME}/bin/hbase canary - write. Sniffing - write. Table ns: canary. The default value size of each put is 1. Treat read / write failure as error. By default, the canary tool only logs read failure, due to e. Retries. Exhausted. Exception. while returning normal exit code. To treat read / write failure as error, you can run canary. Failure. As. Error option. When enabled, read / write failure would result in error. HBASE_HOME}/bin/hbase canary - -treat. Failure. As. Error. Running Canary in a Kerberos- enabled Cluster. To run Canary in a Kerberos- enabled cluster, configure the following two properties in hbase- site. Kerberos credentials are refreshed every 3. Canary runs in daemon mode. To configure the DNS interface for the client, configure the following optional properties in hbase- site. Example 5. 6. Canary in a Kerberos- Enabled Cluster. This example shows each of the properties with valid values.< property> < name> hbase. HOST@YOUR- REALM. COM< /value> < /property> < property> < name> hbase. Health Checker. You can configure HBase to run a script periodically and if it fails N times (configurable), have the server exit. See HBASE- 7. 35. Periodic health check script for configurations and detail. Driver. Several frequently- accessed utilities are provided as Driver classes, and executed by the bin/hbase command. These utilities represent Map. Reduce jobs which run on your cluster. They are run in the following way, replacing Utility. Name with the utility you want to run. This command assumes you have set the environment variable HBASE_HOME to the directory where HBase is unpacked on your server.${HBASE_HOME}/bin/hbase org. Utility. Name. The following utilities are available: Load. Incremental. HFiles. Complete a bulk data load. Copy. Table. Export a table from the local cluster to a peer cluster. Export. Write table data to HDFS. Import. Import data written by a previous Export operation. Import. Tsv. Import data in TSV format. Row. Counter. Count rows in an HBase table. Cell. Counter. Count cells in an HBase table. Verify. Replication. Compare the data from tables in two different clusters. WARNING: It doesn’t work for increment. Column. Values’d cells since the timestamp is changed. Note that this command is in a different package than the others. Each command except Row. Counter and Cell. Counter accept a single - -help argument to print usage instructions. HBase hbck. To run hbck against your HBase cluster run $./bin/hbase hbck. At the end of the command’s output it prints OK or INCONSISTENCY. If your cluster reports inconsistencies, pass - details to see more detail emitted. If inconsistencies, run hbck a few times because the inconsistency may be transient (e. Passing - fix may correct the inconsistency (This is an experimental feature). For more information, see hbck In Depth. The main method on FSHLog offers manual split and dump facilities. Pass it WALs or the product of a split, the content of the recovered.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |