Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
languagejava
titleTopic Level Configs
    public static final String REMOTE_COPY_LAG_MS_CONFIG = "remote.copy.lag.ms";
    public static final String REMOTE_COPY_LAG_MS_DOC = "Controls how long to delay uploading segments to remote storage. " +
            "When set to 0 (default), segments are uploaded as soon as they are eligible (no delay). " +
            "When set to -1, resolves to <code>local.retention.ms</code> (maximum delay). " +
            "When set to a positive value (ms), a segment isbecomes eligible for upload only after the ittime since hasthe beenlatest closedrecord forin atthe leastsegment thisreaches manythe millisecondsvalue. " +
            "The value should not exceed <code>local.retention.ms</code> (local retention time).";

    public static final String REMOTE_COPY_LAG_BYTES_CONFIG = "remote.copy.lag.bytes";
    public static final String REMOTE_COPY_LAG_BYTES_DOC = "Controls size-based delay for uploading segments to remote storage. " +
            "When set to 0 (default), segments are uploaded as soon as they are eligible (no size-based constraintdelay). " +
            "When set to -1, resolves to <code>local.retention.bytes</code> (maximum delay). " +
            "When set to a positive value (bytes), a segment isbecomes eligible for upload only when at least this manythe bytes of log data exist after the segment reach the value. " +
            "The value should not exceed <code>local.retention.bytes</code> (local retention size).";

(2) Two new server configuration items:  log.remote.copy.lag.ms and log.remote.copy.lag.bytes
If a user wants to enable the lazy copy behaviour behavior for all the topics (including the new ones), then they can set this broker level configs. Otherwise,
it will be hard for the user to create the new topics with these configs set when remote storage is enabled.

...