You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@pulsar.apache.org by Apache Pulsar Slack <ap...@gmail.com> on 2019/01/07 09:11:04 UTC
Slack digest for #general - 2019-01-07
2019-01-06 17:21:15 UTC - Adam F: @Adam F has joined the channel
----
2019-01-07 04:03:24 UTC - tigerquoll: @tigerquoll has joined the channel
----
2019-01-07 05:35:58 UTC - murugappan: @murugappan has joined the channel
----
2019-01-07 08:14:06 UTC - Michael-Yu: where is the pulsar ’s schemas medata store, zookeeper or bookkeeper
+1 : Yuvaraj Loganathan
----
2019-01-07 08:48:23 UTC - bossbaby: Hi all, i found error in pulsar:
15:31:02.359 [main] ERROR org.apache.pulsar.client.cli.PulsarClientTool - Namespace missing local cluster name in clusters list: local_cluster=standalone ns=test-tenant/test-namespace clusters=[cluster-1]
how to fix it?
Thanks you all
----
2019-01-07 08:50:48 UTC - Sijie Guo: currently it is stored in bookkeeper. please check : <https://github.com/apache/pulsar/blob/master/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/schema/BookkeeperSchemaStorage.java>
in future, we might be moving the schema metadata store to bookkeeper’s new table service.
+1 : Yuvaraj Loganathan
----
2019-01-07 08:51:54 UTC - Sijie Guo: are you running standalone but creating a namespace with cluster `cluster-1`?
----
2019-01-07 08:53:05 UTC - Sijie Guo: > how to fix it?
```
pulsar-admin namespaces set-clusters test-tenant/test-namespace \
--clusters standalone
```
----
2019-01-07 08:55:28 UTC - bossbaby: no, i run cluster mode
----
2019-01-07 08:55:52 UTC - bossbaby: i was run this cli and result:
Reason: Cluster [standalone] is not in the list of allowed clusters list for tenant [test-tenant]
----
2019-01-07 08:56:34 UTC - Sijie Guo: is your cluster called `standalone`?
----
2019-01-07 08:56:54 UTC - Sijie Guo: if your cluster isn’t called standalone, then there must be some brokers running in standalone mode.
----
2019-01-07 08:57:17 UTC - Sijie Guo: `Cluster [standalone] ` means the broker you are running is in cluster `standalone`
----
2019-01-07 08:57:43 UTC - Sijie Guo: so I would suggest you check your broker processes and also broker configuration to see if you happen to have some brokers running in standalone mode
----
2019-01-07 09:01:34 UTC - bossbaby: i found bug and fixed it but new bug
org.apache.bookkeeper.mledger.ManagedLedgerException: Not enough non-faulty bookies available :disappointed:
----
2019-01-07 09:10:31 UTC - Sijie Guo: There are no enough bookies available. Run “bin/bookkeeper shell listbookies -rw “ to see how many bookie are alive
----