[HDFS-13639] SlotReleaser is not fast enough - ASF JIRA

Voters

Watch issue

Watchers

Create sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 2.4.0, 2.6.0, 3.0.2
Fix Version/s: 3.3.1, 3.4.0
Component/s: hdfs-client
Labels:
None
Environment:

Hide

1. YCSB:

recordcount=2000000000
fieldcount=1
fieldlength=1000
operationcount=10000000

workload=com.yahoo.ycsb.workloads.CoreWorkload

table=ycsb-test
columnfamily=C
readproportion=1
updateproportion=0
insertproportion=0
scanproportion=0

maxscanlength=0
requestdistribution=zipfian

# default
readallfields=true
writeallfields=true
scanlengthdistribution=constan

2. datanode:

-Xmx2048m -Xms2048m -Xmn1024m -XX:MaxDirectMemorySize=1024m -XX:MaxPermSize=256m -Xloggc:$run_dir/stdout/datanode_gc_${start_time}.log -XX:+DisableExplicitGC -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=$log_dir -XX:+PrintGCApplicationStoppedTime -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=80 -XX:+UseCMSInitiatingOccupancyOnly -XX:+CMSParallelRemarkEnabled -XX:+CMSClassUnloadingEnabled -XX:CMSMaxAbortablePrecleanTime=10000 -XX:+CMSScavengeBeforeRemark -XX:+PrintPromotionFailure -XX:+CMSConcurrentMTEnabled -XX:+ExplicitGCInvokesConcurrent -XX:+SafepointTimeout -XX:MonitorBound=16384 -XX:-UseBiasedLocking -verbose:gc -XX:+PrintGCDetails -XX:+PrintHeapAtGC -XX:+PrintGCDateStamps

3. regionserver:

-Xmx10g -Xms10g -XX:MaxDirectMemorySize=10g -XX:MaxGCPauseMillis=150 -XX:MaxTenuringThreshold=2 -XX:+UnlockExperimentalVMOptions -XX:G1NewSizePercent=5 -Xloggc:$run_dir/stdout/regionserver_gc_${start_time}.log -Xss256k -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=$log_dir -verbose:gc -XX:+PrintGC -XX:+PrintGCDetails -XX:+PrintGCApplicationStoppedTime -XX:+PrintHeapAtGC -XX:+PrintGCDateStamps -XX:+PrintAdaptiveSizePolicy -XX:+PrintTenuringDistribution -XX:+PrintSafepointStatistics -XX:PrintSafepointStatisticsCount=1 -XX:PrintFLSStatistics=1 -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=100 -XX:GCLogFileSize=128m -XX:+SafepointTimeout -XX:MonitorBound=16384 -XX:-UseBiasedLocking -XX:+UseG1GC -XX:InitiatingHeapOccupancyPercent=65 -XX:+ParallelRefProcEnabled -XX:ConcGCThreads=4 -XX:ParallelGCThreads=16 -XX:G1HeapRegionSize=32m -XX:G1MixedGCCountTarget=64 -XX:G1OldCSetRegionThresholdPercent=5

block cache is disabled: <property>
<name>hbase.bucketcache.size</name>
<value>0.9</value>
</property>

Show
1. YCSB: recordcount=2000000000 fieldcount=1 fieldlength=1000 operationcount=10000000 workload=com.yahoo.ycsb.workloads.CoreWorkload table=ycsb-test columnfamily=C readproportion=1 updateproportion=0 insertproportion=0 scanproportion=0 maxscanlength=0 requestdistribution=zipfian # default readallfields=true writeallfields=true scanlengthdistribution=constan 2. datanode: -Xmx2048m -Xms2048m -Xmn1024m -XX:MaxDirectMemorySize=1024m -XX:MaxPermSize=256m -Xloggc:$run_dir/stdout/datanode_gc_${start_time}.log -XX:+DisableExplicitGC -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=$log_dir -XX:+PrintGCApplicationStoppedTime -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=80 -XX:+UseCMSInitiatingOccupancyOnly -XX:+CMSParallelRemarkEnabled -XX:+CMSClassUnloadingEnabled -XX:CMSMaxAbortablePrecleanTime=10000 -XX:+CMSScavengeBeforeRemark -XX:+PrintPromotionFailure -XX:+CMSConcurrentMTEnabled -XX:+ExplicitGCInvokesConcurrent -XX:+SafepointTimeout -XX:MonitorBound=16384 -XX:-UseBiasedLocking -verbose:gc -XX:+PrintGCDetails -XX:+PrintHeapAtGC -XX:+PrintGCDateStamps 3. regionserver: -Xmx10g -Xms10g -XX:MaxDirectMemorySize=10g -XX:MaxGCPauseMillis=150 -XX:MaxTenuringThreshold=2 -XX:+UnlockExperimentalVMOptions -XX:G1NewSizePercent=5 -Xloggc:$run_dir/stdout/regionserver_gc_${start_time}.log -Xss256k -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=$log_dir -verbose:gc -XX:+PrintGC -XX:+PrintGCDetails -XX:+PrintGCApplicationStoppedTime -XX:+PrintHeapAtGC -XX:+PrintGCDateStamps -XX:+PrintAdaptiveSizePolicy -XX:+PrintTenuringDistribution -XX:+PrintSafepointStatistics -XX:PrintSafepointStatisticsCount=1 -XX:PrintFLSStatistics=1 -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=100 -XX:GCLogFileSize=128m -XX:+SafepointTimeout -XX:MonitorBound=16384 -XX:-UseBiasedLocking -XX:+UseG1GC -XX:InitiatingHeapOccupancyPercent=65 -XX:+ParallelRefProcEnabled -XX:ConcGCThreads=4 -XX:ParallelGCThreads=16 -XX:G1HeapRegionSize=32m -XX:G1MixedGCCountTarget=64 -XX:G1OldCSetRegionThresholdPercent=5 block cache is disabled: <property> <name>hbase.bucketcache.size</name> <value>0.9</value> </property>

Target Version/s:

3.4.0
Hadoop Flags:

Reviewed

Description

When test the performance of the ShortCircuit Read of the HDFS with YCSB, we find that SlotReleaser of the ShortCircuitCache has some performance issue. The problem is that, the qps of the slot releasing could only reach to 1000+ while the qps of the slot allocating is ~3000. This means that the replica info on datanode could not be released in time, which causes a lot of GCs and finally full GCs.

The fireflame graph shows that SlotReleaser spends a lot of time to do domain socket connecting and throw/catching the exception when close the domain socket and its streams. It doesn't make any sense to do the connecting and closing each time. Each time when we connect to the domain socket, Datanode allocates a new thread to free the slot. There are a lot of initializing work, and it's costly. We need reuse the domain socket.

After switch to reuse the domain socket(see diff attached), we get great improvement(see the perf):

without reusing the domain socket, the get qps of the YCSB getting worse and worse, and after about 45 mins, full GC starts. When we reuse the domain socket, no full GC found, and the stress test could be finished smoothly, the qps of allocating and releasing match.
Due to the datanode young GC, without the improvement, the YCSB get qps is even smaller than the one with the improvement, ~3700 VS ~4200.