-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HBASE-11062 hbtop #476
Merged
Merged
HBASE-11062 hbtop #476
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
# Licensed to the Apache Software Foundation (ASF) under one | ||
# or more contributor license agreements. See the NOTICE file | ||
# distributed with this work for additional information | ||
# regarding copyright ownership. The ASF licenses this file | ||
# to you under the Apache License, Version 2.0 (the | ||
# "License"); you may not use this file except in compliance | ||
# with the License. You may obtain a copy of the License at | ||
# | ||
# http://www.apache.org/licenses/LICENSE-2.0 | ||
# | ||
# Unless required by applicable law or agreed to in writing, software | ||
# distributed under the License is distributed on an "AS IS" BASIS, | ||
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
# See the License for the specific language governing permissions and | ||
# limitations under the License. | ||
|
||
log4j.rootLogger=WARN,console | ||
log4j.threshold=WARN | ||
|
||
# console | ||
log4j.appender.console=org.apache.log4j.ConsoleAppender | ||
log4j.appender.console.target=System.err | ||
log4j.appender.console.layout=org.apache.log4j.PatternLayout | ||
log4j.appender.console.layout.ConversionPattern=%d{ISO8601} %-5p [%t] %c{2}: %m%n | ||
|
||
# ZooKeeper will still put stuff at WARN | ||
log4j.logger.org.apache.zookeeper=ERROR |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,248 @@ | ||
<!--- | ||
Licensed to the Apache Software Foundation (ASF) under one | ||
or more contributor license agreements. See the NOTICE file | ||
distributed with this work for additional information | ||
regarding copyright ownership. The ASF licenses this file | ||
to you under the Apache License, Version 2.0 (the | ||
"License"); you may not use this file except in compliance | ||
with the License. You may obtain a copy of the License at | ||
|
||
http://www.apache.org/licenses/LICENSE-2.0 | ||
|
||
Unless required by applicable law or agreed to in writing, | ||
software distributed under the License is distributed on an | ||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY | ||
KIND, either express or implied. See the License for the | ||
specific language governing permissions and limitations | ||
under the License. | ||
--> | ||
|
||
# hbtop | ||
|
||
## Overview | ||
|
||
`hbtop` is a real-time monitoring tool for HBase like Unix's top command. | ||
It can display summary information as well as metrics per Region/Namespace/Table/RegionServer. | ||
In this tool, you can see the metrics sorted by a selected field and filter the metrics to see only metrics you really want to see. | ||
Also, with the drill-down feature, you can find hot regions easily in a top-down manner. | ||
|
||
## Usage | ||
|
||
You can run hbtop with the following command: | ||
|
||
``` | ||
$ hbase hbtop | ||
``` | ||
|
||
In this case, the values of `hbase.client.zookeeper.quorum` and `zookeeper.znode.parent` in `hbase-site.xml` in the classpath or the default values of them are used to connect. | ||
|
||
Or, you can specify your own zookeeper quorum and znode parent as follows: | ||
|
||
``` | ||
$ hbase hbtop -Dhbase.client.zookeeper.quorum=<zookeeper quorum> -Dzookeeper.znode.parent=<znode parent> | ||
``` | ||
|
||
![Top screen](img/top_screen.gif "Top screen") | ||
|
||
The top screen consists of a summary part and of a metrics part. | ||
In the summary part, you can see `HBase Version`, `Cluster ID`, `The number of region servers`, `Region count`, `Average Cluster Load` and `Aggregated Request/s`. | ||
In the metrics part, you can see metrics per Region/Namespace/Table/RegionServer depending on the selected mode. | ||
The top screen is refreshed in a certain period – 3 seconds by default. | ||
|
||
### Scrolling metric records | ||
|
||
You can scroll the metric records in the metrics part. | ||
|
||
![Scrolling metric records](img/scrolling_metric_records.gif "Scrolling metric records") | ||
|
||
### Command line arguments | ||
|
||
| Argument | Description | | ||
|---|---| | ||
| -d,--delay <arg> | The refresh delay (in seconds); default is 3 seconds | | ||
| -h,--help | Print usage; for help while the tool is running press `h` key | | ||
| -m,--mode <arg> | The mode; `n` (Namespace)|`t` (Table)|r (Region)|`s` (RegionServer), default is `r` (Region) | | ||
|
||
### Modes | ||
|
||
There are the following 4 modes in hbtop: | ||
|
||
| Mode | Description | | ||
busbey marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|---|---| | ||
| Region | Showing metric records per region | | ||
| Namespace | Showing metric records per namespace | | ||
| Table | Showing metric records per table | | ||
| RegionServer | Showing metric records per region server | | ||
|
||
#### Region mode | ||
|
||
In Region mode, the default sort field is `#REQ/S`. | ||
|
||
The fields in this mode are as follows: | ||
|
||
| Field | Description | Displayed by default | | ||
|---|---|---| | ||
| RNAME | Region Name | false | | ||
| NAMESPACE | Namespace Name | true | | ||
| TABLE | Table Name | true | | ||
| SCODE | Start Code | false | | ||
| REPID | Replica ID | false | | ||
| REGION | Encoded Region Name | true | | ||
| RS | Short Region Server Name | true | | ||
| LRS | Long Region Server Name | false | | ||
| #REQ/S | Request Count per second | true | | ||
| #READ/S | Read Request Count per second | true | | ||
| #FREAD/S | Filtered Read Request Count per second | true | | ||
| #WRITE/S | Write Request Count per second | true | | ||
| SF | StoreFile Size | true | | ||
| USF | Uncompressed StoreFile Size | false | | ||
| #SF | Number of StoreFiles | true | | ||
| MEMSTORE | MemStore Size | true | | ||
| LOCALITY | Block Locality | true | | ||
| SKEY | Start Key | false | | ||
| #COMPingCELL | Compacting Cell Count | false | | ||
| #COMPedCELL | Compacted Cell Count | false | | ||
| %COMP | Compaction Progress | false | | ||
| LASTMCOMP | Last Major Compaction Time | false | | ||
|
||
#### Namespace mode | ||
|
||
In Namespace mode, the default sort field is `#REQ/S`. | ||
|
||
The fields in this mode are as follows: | ||
|
||
| Field | Description | Displayed by default | | ||
|---|---|---| | ||
| NAMESPACE | Namespace Name | true | | ||
| #REGION | Region Count | true | | ||
| #REQ/S | Request Count per second | true | | ||
| #READ/S | Read Request Count per second | true | | ||
| #FREAD/S | Filtered Read Request Count per second | true | | ||
| #WRITE/S | Write Request Count per second | true | | ||
| SF | StoreFile Size | true | | ||
| USF | Uncompressed StoreFile Size | false | | ||
| #SF | Number of StoreFiles | true | | ||
| MEMSTORE | MemStore Size | true | | ||
|
||
#### Table mode | ||
|
||
In Table mode, the default sort field is `#REQ/S`. | ||
|
||
The fields in this mode are as follows: | ||
|
||
| Field | Description | Displayed by default | | ||
|---|---|---| | ||
| NAMESPACE | Namespace Name | true | | ||
| TABLE | Table Name | true | | ||
| #REGION | Region Count | true | | ||
| #REQ/S | Request Count per second | true | | ||
| #READ/S | Read Request Count per second | true | | ||
| #FREAD/S | Filtered Read Request Count per second | true | | ||
| #WRITE/S | Write Request Count per second | true | | ||
| SF | StoreFile Size | true | | ||
| USF | Uncompressed StoreFile Size | false | | ||
| #SF | Number of StoreFiles | true | | ||
| MEMSTORE | MemStore Size | true | | ||
|
||
#### RegionServer mode | ||
|
||
In RegionServer mode, the default sort field is `#REQ/S`. | ||
|
||
The fields in this mode are as follows: | ||
|
||
| Field | Description | Displayed by default | | ||
|---|---|---| | ||
| RS | Short Region Server Name | true | | ||
| LRS | Long Region Server Name | false | | ||
| #REGION | Region Count | true | | ||
| #REQ/S | Request Count per second | true | | ||
| #READ/S | Read Request Count per second | true | | ||
| #FREAD/S | Filtered Read Request Count per second | true | | ||
| #WRITE/S | Write Request Count per second | true | | ||
| SF | StoreFile Size | true | | ||
| USF | Uncompressed StoreFile Size | false | | ||
| #SF | Number of StoreFiles | true | | ||
| MEMSTORE | MemStore Size | true | | ||
| UHEAP | Used Heap Size | true | | ||
| MHEAP | Max Heap Size | true | | ||
|
||
### Changing mode | ||
|
||
You can change mode by pressing `m` key in the top screen. | ||
|
||
![Changing mode](img/changing_mode.gif "Changing mode") | ||
|
||
### Changing the refresh delay | ||
|
||
You can change the refresh by pressing `d` key in the top screen. | ||
|
||
![Changing the refresh delay](img/changing_refresh_delay.gif "Changing the refresh delay") | ||
|
||
### Changing the displayed fields | ||
|
||
You can move to the field screen by pressing `f` key in the top screen. In the fields screen, you can change the displayed fields by choosing a field and pressing `d` key or `space` key. | ||
|
||
![Changing the displayed fields](img/changing_displayed_fields.gif "Changing the displayed fields") | ||
|
||
### Changing the sort field | ||
|
||
You can move to the fields screen by pressing `f` key in the top screen. In the field screen, you can change the sort field by choosing a field and pressing `s`. Also, you can change the sort order (ascending or descending) by pressing `R` key. | ||
|
||
![Changing the sort field](img/changing_sort_field.gif "Changing the sort field") | ||
|
||
|
||
### Changing the order of the fields | ||
|
||
You can move to the fields screen by pressing `f` key in the top screen. In the field screen, you can change the order of the fields. | ||
|
||
![Changing the order of the fields](img/changing_order_of_fields.gif "Changing the sort field") | ||
|
||
### Filters | ||
|
||
You can filter the metric records with the filter feature. We can add filters by pressing `o` key for ignoring case or `O` key for case sensitive. | ||
|
||
![Adding filters](img/adding_filters.gif "Adding filters") | ||
|
||
The syntax is as follows: | ||
``` | ||
<Field><Operator><Value> | ||
``` | ||
|
||
For example, we can add filters like the following: | ||
``` | ||
NAMESPACE==default | ||
REQ/S>1000 | ||
``` | ||
|
||
The operators we can specify are as follows: | ||
|
||
| Operator | Description | | ||
|---|---| | ||
| = | Partial match | | ||
| == | Exact match | | ||
| > | Greater than | | ||
| >= | Greater than or equal to | | ||
| < | Less than | | ||
| <= | Less than and equal to | | ||
|
||
You can see the current filters by pressing `^o` key and clear them by pressing `=` key. | ||
|
||
![Showing and clearing filters](img/showing_and_clearing_filters.gif "Showing and clearing filters") | ||
|
||
### Drilling down | ||
|
||
You can drill down the metric record by choosing a metric record that you want to drill down and pressing `i` key in the top screen. With this feature, you can find hot regions easily in a top-down manner. | ||
|
||
![Drilling down](img/driling_down.gif "Drilling down") | ||
|
||
### Help screen | ||
|
||
You can see the help screen by pressing `h` key in the top screen. | ||
|
||
![Help screen](img/help_screen.gif "Help screen") | ||
|
||
## Others | ||
|
||
### How hbtop gets the metrics data | ||
|
||
hbtop gets the metrics from ClusterMetrics which is returned as the result of a call to Admin#getClusterMetrics() on the current HMaster. To add metrics to hbtop, they will need to be exposed via ClusterMetrics. | ||
brfrn169 marked this conversation as resolved.
Show resolved
Hide resolved
|
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's with all this gymnastics building a custom class path? Looks like a land mine waiting to trip up someone who wants to upgrade our dependencies.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any command that needs something beyond our basics (either client or normal service process) has to whitelist the extras it needs.
hbtop largely just needs the shaded client jar, but it has some third-party stuff it uses directly, hence the extra add on.
I think this is the best of not great options given how we currently do packaging.
If you want to discuss improvements to how we do command packaging it's something I'm interested in. A DISCUSS thread or an umbrella jira would probably be a better venue for that