Skip to content

Coordinator console should make use of druid.segmentCache.locations:maxSize for historical nodes #622

@ethanocentricity

Description

@ethanocentricity

The rules for determining available space on a historical node for a segment seem to include both druid.server.maxSize and druid.segmentCache.locations:maxSize.

However, the Coordinator Console shows the Max Size and Percent Used based only on druid.server.maxSize.

It would be useful if the console showed both values to help diagnose "segment too large" errors thrown by the OmniSegmentLoader (when people accidentally set them to different values).

See https://groups.google.com/forum/#!searchin/druid-development/segment$20too$20large/druid-development/w8Q65ZRusi4/kN0JybUtUfAJ

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions