This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Can anyone help on this ... Below attached issue iam getting while producing message to topic...

This message was deleted.

Metrics Question - am using Pulsar 2.6.1 and the metric

bookie_journal_JOURNAL_QUEUE_SIZE

is negative

The metric

bookie_journal_JOURNAL_CB_QUEUE_SIZE

however is positive and the inverse number

This message was deleted.

I have prototyped some schema evolution use cases, and they are working for the most part. I have two questions. I followed the documentation at https://pulsar.apache.org/docs/en/schema-evolution-compatibility/. When

schema_compatibility_strategy

is set to

FORWARD_TRANSITIVE

, I was able to add fields as documented. When I tried to delete an optional field, I get a 409 on the client side. The optional field that I attempted to remove was:

{
  "name": "action",
  "type": [
    "null",
    {
      "type": "string",
      "avro.java.string": "String"
    }
  ]
}

I thought the presence of "null" makes a field optional. Is the above field an optional field?

This message was deleted.

Hi all. As described in the official documentation. I have to list all hosts when initialize-cluster-metadata if I donot have DNS. Any suggestion about how should I do to scale out the cluster? Will the new Broker instance modify the znode while starting?

Hello guys We try to certify the pulsar according the few security standards . We scanned the pulsar image 2.7.0 by WhiteSource Unfortunately , 167 high risk CVE have be discovered in the 55 outdated libraries that were marked is High risk vulnerable . I Attached the exported report with the libraries list. It's "bit" makes our effort to certify the pulsar for the highly secured production environment to be complicated 😞 On the other hand , there is the opened issue about automated security scanning. https://github.com/apache/pulsar/issues/8815 Any change to move this issue forward or at least to upgrade the outdated libraries with high risk?? Could make significant boost to adoption the pulsar by many security regulated environments

The difference in broker CPU usage rate is huge. How can I do it on average? @sijieg

This message was deleted.

This message was deleted.

This message was deleted.

Bookie compaction question - using Apache Pulsar 2.6.1 (Bookkeeper 4.10.0?). We have Major compaction configured every 2 hours

# grep -i ompact bookkeeper.conf | grep -v "#"
compactionRate=1000
minorCompactionThreshold=0.95
minorCompactionInterval=1200
compactionMaxOutstandingRequests=100000
majorCompactionThreshold=1.0
majorCompactionInterval=7200
compactionRateByEntries=1000
compactionRateByBytes=1000000

but we only saw the

Enter major compaction

log line twice in the last 3 days (see image below) The GarbageCollectorThread does appear to be still running however

platform-pulsar-bookkeeper-0 platform-pulsar-bookkeeper 13:00:20.504 [GarbageCollectorThread-11-1] INFO  org.apache.bookkeeper.bookie.EntryLogCompactor - Removing entry log 2198 after compaction
platform-pulsar-bookkeeper-0 platform-pulsar-bookkeeper 13:00:20.600 [GarbageCollectorThread-11-1] INFO  org.apache.bookkeeper.bookie.GarbageCollectorThread - Removing entry log metadata for 2198
platform-pulsar-bookkeeper-0 platform-pulsar-bookkeeper 13:04:00.379 [GarbageCollectorThread-11-1] INFO  org.apache.bookkeeper.bookie.EntryLogManagerBase - Creating a new entry log file : createNewLog = false, reachEntryLogLimit = true
platform-pulsar-bookkeeper-0 platform-pulsar-bookkeeper 13:04:00.379 [GarbageCollectorThread-11-1] INFO  org.apache.bookkeeper.bookie.EntryLogManagerBase - Flushing entry logger 2636 back to filesystem, pending for syncing entry loggers : [BufferedChannel{logId=2636, logFile=data/bookkeeper/ledgers/current/a4c.log, ledgerIdAssigned=-1}].
platform-pulsar-bookkeeper-0 platform-pulsar-bookkeeper 13:06:34.287 [GarbageCollectorThread-11-1] INFO  org.apache.bookkeeper.bookie.EntryLogCompactor - Removing entry log 2142 after compaction
platform-pulsar-bookkeeper-0 platform-pulsar-bookkeeper 13:06:34.320 [GarbageCollectorThread-11-1] INFO  org.apache.bookkeeper.bookie.GarbageCollectorThread - Removing entry log metadata for 2142

Just wondering why if the thread is still running why it isn't doing a major (or minor) collection?

This message was deleted.

This message was deleted.

This message was deleted.