This message was deleted.

Datasets in pulsar can grow beyond the retention size settings, mainly when the Mb size is low. This is because segments are kept open until they receive 50k messages or 4 hours pass. Only after a segment is closed is it eligible for deletion.

Many thanks for this, make senses now. Is it ok to tweak these params just in the standalone dev env alone using - name: PULSAR_PREFIX_backlogQuotaDefaultLimitBytes value: “314572800” #300Mb - name: PULSAR_PREFIX_backlogQuotaDefaultRetentionPolicy value: “consumer_backlog_eviction” - name: PULSAR_PREFIX_defaultRetentionTimeInMinutes value: “0” - name: PULSAR_PREFIX_defaultRetentionSizeInMB value: “0" - name: PULSAR_PREFIX_ttlDurationDefaultInSeconds value: “120” - name: PULSAR_PREFIX_managedLedgerMaxEntriesPerLedger value: “5000" - name: PULSAR_PREFIX_managedLedgerCursorMaxEntriesPerLedger value: “5000” - name: PULSAR_PREFIX_managedLedgerMaxLedgerRolloverTimeMinutes value: “30" - name: PULSAR_PREFIX_managedLedgerCursorRolloverTimeInSeconds value: “600” - name: PULSAR_PREFIX_managedLedgerMaxSizePerLedgerMbytes value: “500"