Hi guys, seems like `druid.segmentCache.numLoading...
# troubleshooting
j
Hi guys, seems like
druid.segmentCache.numLoadingThreads
on historical node is not making any difference on how many threads will be used to load segments from S3 in parallel. I am using latest Druid version, by changing this property to 16, it still uses only 1 thread to download the segment from s3, any pointers ?