Skip to content

Incorrect sharding when cluster etc. is set in dimensions #32

@matthayter

Description

@matthayter

The Messages.StatisticSetRecord no longer requires the cluster, service and host to be present in their respective fields, instead allowing them to be conveyed via a dimension key-value. The AggClientConnection class defers to the dimensions for retrieval of the cluster, service and host; however, the AggMessageExtractor does not, and still looks in the now-optional fields of the StatisticSetRecord message.

This would appear to be a bug, causing incorrect sharding when the messages sent from MAD have opted to use dimensions to convey cluster, service and host.

Can someone sanity check me on this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions