You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There can be clock skew on backend machine resulting in start time and end time not being accurate values. Since we are depending on vertx timer for expiry of aggregation window(which uses stable clock), we know that expiry will happen correctly regardless of wall clock skew. So, additionally capturing duration of window in java objects. This needs to be added as a new field and serialized in aggregated profile proto as well.
Changes in aggregation window were made in this commit: a525979
The text was updated successfully, but these errors were encountered:
There can be clock skew on backend machine resulting in start time and end time not being accurate values. Since we are depending on vertx timer for expiry of aggregation window(which uses stable clock), we know that expiry will happen correctly regardless of wall clock skew. So, additionally capturing duration of window in java objects. This needs to be added as a new field and serialized in aggregated profile proto as well.
Changes in aggregation window were made in this commit: a525979
The text was updated successfully, but these errors were encountered: