Re: [I] [Bug] Message loss on bookies and brokers restart [pulsar]

["szkoludasebastian (via GitHub)" <gi...@apache.org>]

szkoludasebastian commented on issue #22709:
URL: https://github.com/apache/pulsar/issues/22709#issuecomment-2145063541

   here we have our broker configuration which we set by config map:
   ```
     brokerDeduplicationEnabled: "false"
     brokerDeleteInactiveTopicsEnabled: "false"
     brokerServicePort: "6650"
     clusterName: integ-pulsar
     configurationStoreServers: integ-pulsar-zookeeper:2181
     defaultNumberOfNamespaceBundles: "16"
     exposeTopicLevelMetricsInPrometheus: "true"
     functionsWorkerEnabled: "false"
     loadBalancerNamespaceMaximumBundles: "512"
     managedLedgerDefaultAckQuorum: "2"
     managedLedgerDefaultEnsembleSize: "3"
     managedLedgerDefaultWriteQuorum: "3"
     managedLedgerMaxLedgerRolloverTimeMinutes: "60"
     managedLedgerMinLedgerRolloverTimeMinutes: "1"
     managedLedgerOffloadDriver: aws-s3
     maxUnackedMessagesPerConsumer: "500000"
     maxUnackedMessagesPerSubscription: "2000000"
     numHttpServerThreads: "8"
     s3ManagedLedgerOffloadBucket: tiered-storage-us-east-1
     s3ManagedLedgerOffloadRegion: us-east-1
     s3ManagedLedgerOffloadRole: integ-broker-role
     s3ManagedLedgerOffloadRoleSessionName: pulsar-tiered-storage-offload
     statusFilePath: /pulsar/status
     subscriptionExpirationTimeMinutes: "43800"
     systemTopicEnabled: "true"
     topicLevelPoliciesEnabled: "true"
     webServicePort: "8080"
     zooKeeperSessionTimeoutMillis: "30000"
     zookeeperServers: integ-pulsar-zookeeper:2181
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org