lukoou3 opened a new issue, #16265: URL: https://github.com/apache/druid/issues/16265
Is druid.segmentCache.locations is used to configure the maximum storage size for hot data? config druid.segmentCache.locations 300g, when data increases， kafka ingestion task fail: ``` WARN [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [15] Segments ```` ### Affected Version 26.0.0. ### Description - Cluster size : 5 - Configurations in use: config druid.segmentCache.locations 300g, deep-storage: hdfs when data increases， kafka ingestion task fail: ``` WARN [coordinator_handoff_scheduled_0] org.apache.druid.segment.handoff.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for [15] Segments ```` historical segmentCache.locations Usage : 100% Is druid.segmentCache.locations is used to configure the maximum storage size for hot data? Delete cold data when there is not enough space, and only pull it from HDFS when querying cold data? Do druid.segmentCache.locations need to store all undeleted data, not just hot data? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
