Hbase ganglia monitoring configuration and hbaseganglia monitoring

Source: Internet
Author: User
Tags dns names

Hbase ganglia monitoring configuration and hbaseganglia monitoring
Hbase ganglia monitoring hbase Configuration

*.sink.ganglia.class=org.apache.hadoop.metrics2.sink.ganglia.GangliaSink31  *.sink.ganglia.period=10  hbase.sink.ganglia.period=10  hbase.sink.ganglia.servers=239.2.11.71:8649hbase.class=org.apache.hadoop.metrics2.sink.ganglia.GangliaSink31hbase.period=10hbase.servers==239.2.11.71:8649jvm.class=org.apache.hadoop.metrics2.sink.ganglia.GangliaSink31jvm.period=10jvm.servers==239.2.11.71:8649rpc.class=org.apache.hadoop.metrics2.sink.ganglia.GangliaSink31rpc.period=10rpc.servers==239.2.11.71:8649

After the configuration is modified, restart the cluster to view the corresponding monitoring information in ganglia.
Note:
The IP address in the preceding configuration item is the IP address specified by mcast_join in the gmond. conf file:

/* Feel free to specify as many udp_send_channels as you like.  Gmond   used to only support having a single channel */udp_send_channel {  #bind_hostname = yes # Highly recommended, soon to be default.                       # This option tells gmond to use a source address                       # that resolves to the machine's hostname.  Without                       # this, the metrics may appear to come from any                       # interface and the DNS names associated with                       # those IPs will be used to create the RRDs.  mcast_join = 239.2.11.71  port = 8649  ttl = 1}
###

Hbase metric item

Hbase. regionserver. blockCacheCount: Number of cache blocks in the memory. The number of StoreFiles (HFiles) blocks in the cache.

Hbase. regionserver. blockCacheEvictedCount: The number of blocks released from the cache because the heap size limit is exceeded.

Hbase. regionserver. blockCacheFree: available cache block capacity.

Hbase. regionserver. blockCacheHitCachingRatio: cache block hit rate (0-100 ). The read cache hit rate is configured to view the cache (for example, cacheblocks = true ).

Hbase. regionserver. blockCacheHitCount: Number of chunks read by StoreFiles (HFiles) from the cache.

Hbase. regionserver. blockCacheHitRatio: cache block hit rate (0-100). This includes all read requests, although cacheBlocks = false reads are counted as cache loss.

Hbase. regionserver. blockCacheMissCount: Number of chunks requested by StoreFiles but not read from the cache.

Hbase. regionserver. blockCacheSize: The Block cache capacity in the memory, especially the memory capacity occupied by blockcache.

Hbase. regionserver. compactionQueueSize: the size of the Compaction queue, which is used for the number of stores in the RegionServer of compaction.

Hbase. regionserver. flushQueueSize: Number of region queues waiting for the flush operation in MemStore.

Hbase. regionserver. fsReadLatency_avg_time: File System latency (MS ). Average read time from HDFS.

Hbase. regionserver. memstoreSizeMB: total capacity (MB) of all memstores in the current RegionServer ).

Hbase. regionserver. requests: Total number of Read and Write requests. A request is equivalent to a RegionServer RPC call, so a Get request is equivalent to a request, but even if the caching value of Scan is set to 1000, each "Next" call to SCAN is equivalent to only one request (for example, non-rows ). For big data block requests, each HFile corresponds to one request.

Hbase. regionserver. storefileIndexSizeMB: total size of the index of the StoreFile in RegionServer (MB ).

Detailed metrics view http://hbase.apache.org/book.html#rs_metrics

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.