CB Response: Solr optimization job skipping all unoptimized cores
book
Article ID: 290370
calendar_today
Updated On:
Products
Carbon Black EDR (formerly Cb Response)
Issue/Introduction
- SolrTimePartitioningOptimizeMaxSegments manually adjusted from defaults
- Solr optimize logs in /var/log/cb/job-runner/job-runner.log shows all cores are skipped
Environment
- CB Response Server: 6.2 and Higher
Cause
SolrTimePartitioningOptimizeMaxSegments set higher than the largest un-optimized core
Resolution
- Edit /etc/cb/cb.conf
- Update SolrTimePartitioningOptimizeMaxSegments to preferred size
- Restart services
Feedback
thumb_up
Yes
thumb_down
No