HBase Read Path openinx@apache.org Abstract ❏ Client Side ❏ Server Side ❏ Tuning Part-1 Client Side HBase Client ClientScanner ClientScanner cache(queue) scanner.next() RegionServer-0 RegionServer-1 (old generation) ● Less mixed GC(s) and shorter STW time. End-to-end offheap on the read-path (HBASE-11425) BucketCache StoreFileScanner Copy the Block from BucketCache(offheap) to onheap. Rpc Handler accumulate multiple results until reach max result size even if reach batch limit ○ Related issue: HBASE-21206 ● BlockSize ? Part-3 Tuning Tuning ● Read Distribution ● Locality ● Short Circuit Read

HBase Practice At Xiaomi huzheng@xiaomi.com About This Talk ● Async HBase Client ○ Why Async HBase Client ○ Implementation ○ Performance ● How do we tuning G1GC for HBase ○ CMS vs G1 ○ Tuning Tuning G1GC ○ G1GC in XiaoMi HBase Cluster Part-1 Async HBase Client Why Async HBase Client ? Request-1 Response-1 Request-2 Response-2 Request-3 Response-3 Request-4 Response-4 Request-1 66% Availability: 0% Why Async HBase Client ? ● Region Server / Master STW GC ● Slow RPC to HDFS ● Region Server Crash ● High Load ● Network Failure BTW: HBase may also suffer from fault amplification

HBase Practice At XiaoMi tianjy1990@gmail.com openinx@apache.org Part-1 Problems In Practice Problems in XiaoMi ❏ Problem 1. How to satisfy the regular demand of scanning table without affecting analysis need to scan a large number of data from hbase ❏ They are executed by mapreduce or spark, that put a heavy burden on HBase Scan snapshot directly ❏ HBase already provides this feature: TableSnapshotInputFormat TableSnapshotInputFormat (ClientSideRegionScanner) ❏ Construct regions by snapshot files ❏ Read data without any HBase RPC requests ❏ Required READ access to reference files and HFiles Snapshot ACL ❏ HDFS ACL could

Scaling a Multi-Tenant k8s Cluster in a Telco Pablo Moncada October 28, 2020 About MasMovil group ● 4th telecom company in Spain ● Provides voice and broadband services to +12M customers ● Several Services +3k CPU +2k Mem +5TB Nodes +300 kube-proxy replacement NetworkPolicy logging Multi-cluster DNS Aware NetworkPolicy Increased Istio security External Services TLS visibility Performance

Kubernetes cluster using CSI Driver on DELL EMC PowerFlex September 2021 H18899 White Paper Abstract This white paper describes the deployment of a SUSE Rancher Kubernetes Cluster on the Dell PowerFlex Engineering Validated Copyright 2 SUSE Rancher and RKE Kubernetes cluster using CSI Driver on DELL EMC PowerFlex White Paper The information in this publication is provided is subject to change without notice. Contents 3 SUSE Rancher and RKE Kubernetes cluster using CSI Driver on DELL EMC PowerFlex White Paper Contents Executive Summary ........

HBASE-21879 Read HFile ’s Block into ByteBuffer directly. 1. Background For reducing the Java GC impact to p99/p999 RPC latency, HBase 2.x has made an offheap read and write path. The KV are allocated Case In above pictures, the p999 latency is almost the same as G1GC STW cost (~100ms). After HBASE-11425​ , almost all memory allocations should be in the offheap, there should be rarely heap allocation As the basic idea part said, the first thing is to design a global ByteBuffAllocator. In ​HBASE-11425​ , we have introduced an offheap memory management policy as following: 1. Set a max memory

clear view of what end users are doing, ensure authentication, authorization, and auditing for both cluster and data security, and so forth. In general, the complete ecosystem of Kyuubi falls into the hierarchies module plays the role of a unified gateway. The server enables simplified, secure access to any cluster resource through an entry point to deploy different workloads for end(remote) users. Behind this The resource acquirement and data and metadata access all happen within their own engine. Thus, cluster managers and storage providers can easily guarantee data and resource security. Besides, Kyuubi also

clear view of what end users are doing, ensure authentication, authorization, and auditing for both cluster and data security, and so forth. In general, the complete ecosystem of Kyuubi falls into the hierarchies module plays the role of a unified gateway. The server enables simplified, secure access to any cluster resource through an entry point to deploy different workloads for end(remote) users. Behind this The resource acquirement and data and metadata access all happen within their own engine. Thus, cluster managers and storage providers can easily guarantee data and resource security. Besides, Kyuubi also

clear view of what end users are doing, ensure authentication, authorization, and auditing for both cluster and data security, and so forth. In general, the complete ecosystem of Kyuubi falls into the hierarchies module plays the role of a unified gateway. The server enables simplified, secure access to any cluster resource through an entry point to deploy different workloads for end(remote) users. Behind this The resource acquirement and data and metadata access all happen within their own engine. Thus, cluster managers and storage providers can easily guarantee data and resource security. Besides, Kyuubi also

clear view of what end users are doing, ensure authentication, authorization, and auditing for both cluster and data security, and so forth. In general, the complete ecosystem of Kyuubi falls into the hierarchies module plays the role of a unified gateway. The server enables simplified, secure access to any cluster resource through an entry point to deploy different workloads for end(remote) users. Behind this The resource acquirement and data and metadata access all happen within their own engine. Thus, cluster managers and storage providers can easily guarantee data and resource security. Besides, Kyuubi also