- #### remote.log.metadata.consume.wait.ms

  The amount of time in milliseconds to wait for the local consumer to receive the published event.

  Type: | long
  Default: | 120000 (2 minutes)
  Valid Values: | [0,...]
  Importance: | low

- #### remote.log.metadata.initialization.retry.interval.ms

  The retry interval in milliseconds for retrying RemoteLogMetadataManager resources initialization again.

  Type: | long
  Default: | 100
  Valid Values: | [0,...]
  Importance: | low

- #### remote.log.metadata.initialization.retry.max.timeout.ms

  The maximum amount of time in milliseconds for retrying RemoteLogMetadataManager resources initialization. For TopicBasedRemoteLogMetadataManager's initialization, the timer starts after this local broker is ready to process requests (primarily for ensuring the local cluster is ready when metadata is stored locally as an internal topic). If initialization fails within this timeout, this broker process will terminate.

  Type: | long
  Default: | 120000 (2 minutes)
  Valid Values: | [0,...]
  Importance: | low

- #### remote.log.metadata.topic.num.partitions

  The number of partitions for remote log metadata topic.

  Type: | int
  Default: | 50
  Valid Values: | [1,...]
  Importance: | low

- #### remote.log.metadata.topic.replication.factor

  Replication factor of remote log metadata topic.

  Type: | short
  Default: | 3
  Valid Values: | [1,...]
  Importance: | low

- #### remote.log.metadata.topic.retention.ms

  Retention of remote log metadata topic in milliseconds. Default: -1, that means unlimited. Users can configure this value based on their use cases. To avoid any data loss, this value should be more than the maximum retention period of any topic enabled with tiered storage in the cluster.

  Type: | long
  Default: | -1
  Valid Values: |
  Importance: | low