Getting Topic policies cache have not init Exception

[shashrath]

Hi Everyone, Getting the below error while updating schema.

I have checked the github issue which is related to this, but that was fixed in this version. Not sure what I am missing here. I have tried rolling restart of all brokers. Prevously that used to fix this but this time it hadn't worked.

Please let me know if you need any other information regarding this.

Pulsar Version : 2.10.2

\n --- An unexpected error occurred in the server ---\n\nMessage: org.apache.pulsar.broker.service.BrokerServiceException$TopicPoliciesCacheNotInitException: Topic policies cache have not init.\n\nStacktrace:\n\njava.util.concurrent.CompletionException: org.apache.pulsar.broker.service.BrokerServiceException$TopicPoliciesCacheNotInitException: Topic policies cache have not init.\n\tat java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:292)\n\tat java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:308)\n\tat java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:607)\n\tat java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:591)\n\tat java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:488)\n\tat java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1990)\n\tat org.apache.pulsar.client.util.RetryUtil.lambda$executeWithRetry$2(RetryUtil.java:53)\n\tat java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:774)\n\tat java.util.concurrent.CompletableFuture.uniWhenCompleteStage(CompletableFuture.java:792)\n\tat java.util.concurrent.CompletableFuture.whenComplete(CompletableFuture.java:2153)\n\tat org.apache.pulsar.client.util.RetryUtil.executeWithRetry(RetryUtil.java:48)\n\tat org.apache.pulsar.client.util.RetryUtil.lambda$executeWithRetry$1(RetryUtil.java:57)\n\tat java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)\n\tat java.util.concurrent.FutureTask.run(FutureTask.java:266)\n\tat java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)\n\tat java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)\n\tat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)\n\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)\n\tat io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat java.lang.Thread.run(Thread.java:748)\nCaused by: org.apache.pulsar.broker.service.BrokerServiceException$TopicPoliciesCacheNotInitException: Topic policies cache have not init.\n\tat org.apache.pulsar.broker.service.SystemTopicBasedTopicPoliciesService.getTopicPolicies(SystemTopicBasedTopicPoliciesService.java:209)\n\tat org.apache.pulsar.broker.service.TopicPoliciesService.lambda$getTopicPoliciesAsyncWithRetry$0(TopicPoliciesService.java:100)\n\t... 10 more\n"
}

Broker Logs

2025-01-20T08:03:07,621+0000 [main-EventThread] INFO  org.apache.pulsar.broker.systopic.NamespaceEventsSystemTopicFactory - Create topic policies system topic client persistent://demotenant/demonamespace/__change_events
2025-01-20T08:03:07,781+0000 [pulsar-io-4-12] WARN  org.apache.pulsar.client.impl.PulsarClientImpl - [persistent://demotenant/demonamespace/__change_events] Failed to get partitioned topic metadata
2025-01-20T08:03:08,806+0000 [pulsar-io-4-15] WARN  org.apache.pulsar.client.impl.PulsarClientImpl - [persistent://demotenant/demonamespace/__change_events] Failed to get partitioned topic metadata
2025-01-20T08:03:10,706+0000 [pulsar-io-4-3] WARN  org.apache.pulsar.client.impl.PulsarClientImpl - [persistent://demotenant/demonamespace/__change_events] Failed to get partitioned topic metadata
2025-01-20T08:03:13,576+0000 [pulsar-io-4-7] WARN  org.apache.pulsar.client.impl.PulsarClientImpl - [persistent://demotenant/demonamespace/__change_events] Failed to get partitioned topic metadata
2025-01-20T08:03:16,472+0000 [pulsar-io-4-10] WARN  org.apache.pulsar.client.impl.PulsarClientImpl - [persistent://demotenant/demonamespace/__change_events] Failed to get partitioned topic metadata
2025-01-20T08:03:16,473+0000 [pulsar-io-4-10] ERROR org.apache.pulsar.broker.service.SystemTopicBasedTopicPoliciesService - [demotenant/demonamespace] Failed to create reader on __change_events topic

[lhotari]

I have checked the github issue which is related to this, but that was fixed in this version. Not sure what I am missing here. I have tried rolling restart of all brokers. Prevously that used to fix this but this time it hadn't worked.

Please let me know if you need any other information regarding this.

Pulsar Version : 2.10.2

@shashrath In the Apache Pulsar open source project, we don't support 2.10.x any more. "Support" is defined this way in the project:

The Apache Pulsar project accepts issue reports for supported versions. Issue reporters are requested to upgrade to a supported version for both Pulsar clients and Pulsar clusters before filing issue reports. Commercial vendors around Apache Pulsar may offer paid options for users requiring security and bug fix support for previous release versions.

After 2.10.2 there are hundreds of improvements, fixes and also fixes for multiple critical security issues.

I'd recommend upgrading to a supported Pulsar version and reporting an issue if the problem persists.