Skip to content

ClockSkewTimestampSample is missing from the ProtoStream schema #55238

Description

@ahus1

Before reporting an issue

  • I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.

Area

infinispan

Bug Description

ClockSkewTimestampSample, introduced with the clock skew detection in #54284, is annotated with @ProtoTypeId but is not listed in includeClasses of KeycloakModelSchema. It is therefore missing from the generated ProtoStream schema and cannot be marshalled. Additionally, the record has no explicit @ProtoField numbers, so the wire format depends on the order of the record components.

Version

nightly (main, 27.0.0)

Expected behavior

The clock skew sample is published to the work cache and received by the other nodes, which log a warning if their clocks differ by more than the threshold.

Actual behavior

The sample is not part of the marshalling schema. As soon as it needs to be serialized, which is the case with more than one node or with a remote cache, publishing it is expected to fail with a marshalling error on every sampling interval, and no clock skew is ever reported. With a single node nothing is serialized, so it goes unnoticed. The existing ClockSkewDetectionTest only puts the sample into the local cache, so it doesn't detect this.

How to Reproduce?

  1. Start two Keycloak nodes in the same cluster from main.
  2. Wait for the clock skew sampling interval (60 seconds by default).
  3. Observe the errors from ClockSkewDetectionTask in the log.

This has been derived from the code and not yet reproduced with a running two-node cluster.

Anything else?

A fix is proposed in #55235. For rolling updates from 26.8 to 27.0, 26.8 nodes need the class and the type ID registered as well, see #55231.

Activity

  1. added
    area/infinispanInfinispan — distributed caches, clustering, JGroups, cross-site replication
    on Nov 16, 2026
  2. added a commit that references this issue on Nov 16, 2026
    a733f3f
  3. added theissue type on Nov 16, 2026
  4. self-assigned this
    on Nov 16, 2026
  5. added a commit that references this issue on Nov 17, 2026
    df3331a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Fields

No fields configured for bug.

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions