sasounda opened a new issue #5577:
URL: https://github.com/apache/druid/issues/5577
After seeing this error in Druid historical
```
Caused by: com.metamx.common.ISE:
Segment[timeseries_dogstatsd_counter_2018-04-04T16:00:00.000Z_2018-04-04T17:00:00.000Z_2018-04-04T16:00:00.000Z_1528210995:152,770,889]
too large for storage[/var/tmp/druid/indexCache:22,010].
```
, we notice that the historical node stops loading new segments from
realtime and the realtime nodes starts accumulating segments.
Our `maxSize` settings goes like this and we had enough free disk space.
```
druid.server.maxSize=882159184076
druid.segmentCache.locations=[{"path":"/var/tmp/druid/indexCache","maxSize":882159184076}]
```
Restarting Druid historical fixes the issue. We suspect that there is
something going wrong with how Druid calculates the available size i.e.,
`22,010`.
--
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.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
