jwitko commented on code in PR #13747:
URL: https://github.com/apache/druid/pull/13747#discussion_r1106323308
##########
helm/druid/values.yaml:
##########
@@ -193,7 +233,7 @@ historical:
druid_processing_numMergeBuffers: 2
druid_processing_numThreads: 1
# druid_monitoring_monitors:
'["org.apache.druid.client.cache.CacheMonitor",
"org.apache.druid.server.metrics.HistoricalMetricsMonitor",
"org.apache.druid.server.metrics.QueryCountStatsMonitor"]'
- # druid_segmentCache_locations:
'[{"path":"/var/druid/segment-cache","maxSize":300000000000}]'
+ # druid_segmentCache_locations:
'[{"path":"/opt/druid/var/druid/segment-cache","maxSize":300000000000}]'
Review Comment:
That is the bullet point in the description
```
Fix historical commented config druid_segmentCache_locations to match PVC
mount path. In it's current form it breaks the historical pod when uncommented
due to lack of permissions to create directory.
```
The container did not have permissions to create/write to
`/var/druid/segment-cache`. `/opt/druid/var/driuid/segment-cache` is inside of
the defined PVC mounted volume path and so the application would have the
ability to write there as well it will be captured by the persistent volume and
persist through pod restarts.
--
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]
