Skip to content

Conversation

@jakobht
Copy link
Member

@jakobht jakobht commented Oct 23, 2025

What changed?

  • Added metadata field (map<string, string>) to HeartbeatRequest proto
  • Implemented server-side validation (max 32 keys, 128 char keys, 512KB values)
  • Added ETCD storage support with atomic transaction updates

Why?
Enable executors to attach generic metadata to heartbeat requests for flexible context sharing.

How did you test it?
Added unit tests for metadata validation and ETCD storage integration.

Potential risks
Low - new optional field, no changes to existing functionality.

Release notes
None - experimental shard distributor feature.

Documentation Changes
None required.

Signed-off-by: Jakob Haahr Taankvist <[email protected]>

_maxMetadataKeys = 32
_maxMetadataKeyLength = 128
_maxMetadataValueSize = 512 * 1024 // 512KB
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should move these values to configuration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants