Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[pulsar-broker] Policies not found

See original GitHub issue

We got this exception in our production logs:

Policies not found for myTenant/myNamespace namespace
Reason: Policies not found for myTenant/myNamespace namespace

We were able to reproduce it by running this command:

bin/pulsar-admin --admin-url http://broker12.example.com:8080 topics stats persistent://myTenant/myNamespace/myTopic

However, we were only able to reproduce it by running that command on that particular broker (broker12).

This incident happened at the same time as: https://github.com/apache/pulsar/issues/6492 and https://github.com/apache/pulsar/issues/6054

Issue Analytics

State:
Created 4 years ago
Comments:6 (5 by maintainers)

Top GitHub Comments

3reactions

lonerzzzcommented, Mar 6, 2020

Was just looking into a similar issue for my own system and saw your post… I identified the problem by connecting with the zookeeper client to the different zookeeper servers. I saw that the appropriate namespace entry was missing under the /namespace path on one of the zookeeper servers. The zookeeper server had lost sync with the others zookeeper servers.

To resolve, I had to clean the snapshot and log files for the out-of=sync zookeeper and restart it. It then resynced with the other servers. The error did not come out after that.

Hope this helps.

0reactions

tisonkuncommented, Nov 10, 2022

Closed as stale. Feel free to reopen it if it’s still relevant for maintained versions.

Top Results From Across the Web

org.apache.pulsar.broker.web.RestException: Policies not ...

1 Answer 1 ... You need to ensure that the tenant and namespace exist that you're trying to deploy the function/sink/source into. If...

Managing Namespaces - Apache Pulsar

Namespace isolation You can use the Pulsar isolation policy to allocate resources (broker and bookie) for a namespace.

Deep Dive into Data Placement Policies - StreamNative

Pulsar brokers not only provide message services, but also offer message storage isolation with the help of BookKeeper clients. For message ...

org.apache.pulsar.broker.admin.impl.PersistentTopicsBase ...

POLICIES ; import static org.apache.pulsar.common.util. ... NOT_FOUND, "Namespace does not exist"); } catch (Exception e) { log.error("[{}] Failed to get ...

Add system topic check when delete namespace bundle.

PulsarWebResource - Policies not found for sample/ns1 namespace > 2021-12-16T16:49:04,065+0800 ... at org.apache.pulsar.broker.web.