09-04-2017 05:39 AM
Can you suggest on the below scenario
The requirement from Customer side was to establish a maximum of 40 k concurrent connections in HBase with an effective response time of 3 seconds. Users would be accessing database using mobile application expecting a reasonable response time for reading and writing the data (no retention period was specified by Customer hence we considered the growing data in future). HBase was used as the database for the Proof of Concept thinking there would be considerable amount of data and real time processing would also be required.
The Feasibility of establishing the concurrent connections using HBase in different ways was checked and details are given below. The distribution used is cloudera and the environment was in Azure cloud.
Different Parameters we set in Cloudera Manager is as below
ZooKeeper Session Timeout : zookeeper.session.timeout -60000
HBase Client Scanner Caching : hbase.client.scanner.caching - 100
HBase Master Handler Count : hbase.master.handler.count - 25
HBase RegionServer Handler Count : hbase.regionserver.handler.count -10000
Java Heap Size of HBase REST Server in Bytes - 1 GiB
Java Heap Size of HBase RegionServer in Bytes - 16 GiB
Java Heap Size of ZooKeeper Server in Bytes - 1 GiB
Maximum Client Connections : maxClientCnxns - 0
Maximum Session Timeout : maxSessionTimeout - 60000