![]() ![]() The initial testing with the G1GC collector has shown very promising results with heaps over 100 GB is size. HBase currently can use about 16–24 GB of memory for the heap, though that will change with Java 7 and the G1GC algorithm. The hardware requirements for an HBase-only deployment are cost friendly compared to a large, multitenant deployment. This means starting with the hardware and then the network before moving on to operating system, HDFS, and finally HBase. You need to consider how much data is ingested daily, the total data retention time, and total data size over the lifetime of the project.Īfter fully understanding these project requirements, we can move on to cluster sizing.īecause HBase relies on HDFS, it is important to take a bottom-up approach when designing an HBase cluster. You should have an SLA that guarantees fully quantified read and write latencies, and understanding the tolerance for variance. This requires understanding general concurrency, usage patterns, and ingress/egress workloads. These requirements should be broken down into three categories: Workload You will want to make sure to understand both the read and the write access patterns before attempting to size the cluster.īecause it involves taking numerous aspects into consideration, proper HBase sizing can be challenging.īefore beginning cluster sizing, it’s important to analyze the requirements for the project. Sizing an HBase cluster is a fine art that requires an understanding of the application needs prior to deploying. ![]() Meanwhile, a properly sized and tuned HBase cluster will perform better and meet SLAs on a consistent level because the internals will have less fluctuation, which in turn means fewer compactions (major and minor), fewer region splits, Many clusters that are undersized tend to suffer from client timeouts, RegionServer failures, and longer recovery times. In addition to negatively impacting performance, sizing an HBase cluster incorrectly will reduce stability. We will discuss schema design in Part II. This chapter will focus on the sizing considerations to take into account when building an application. The two most important aspects of building an HBase appplication are sizing and schema design. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |