2019-02-12 14:48:28 UTC - Matteo Merli: That is what I’m referring to with “no total order”, but messages coming from 1 particular region will appear in order, in all regions ---- 2019-02-12 18:09:09 UTC - Karthik Palanivelu: Team, Can you please let me know the importance of Intialize Cluster data because even if I give a wrong url in the broker, it still works fine? Without this config, bookies are not able to start. ---- 2019-02-12 18:25:11 UTC - Matteo Merli: Yes, this URL is mostly used for geo-replication purposes (to know where other clusters are). You can still correct the URL at any time later ---- 2019-02-12 18:29:50 UTC - Karthik Palanivelu: So this is applicable only for Asynchronous replication and not for Synchronous application. Please correct me if I am wrong ---- 2019-02-12 18:31:38 UTC - Matteo Merli: It’s only used in async replication ---- 2019-02-12 18:33:37 UTC - Karthik Palanivelu: Thanks @Matteo Merli ---- 2019-02-12 18:33:59 UTC - Karthik Palanivelu: Team, do you have any roadmap for integrating pulsar with Debezium? ---- 2019-02-12 18:34:38 UTC - vinay Parekar: @vinay Parekar has joined the channel ---- 2019-02-12 19:02:42 UTC - Matteo Merli: > Team, do you have any roadmap for integrating pulsar with Debezium?
Yep! This is going out this week with 2.3 release! ---- 2019-02-12 19:13:10 UTC - Karthik Palanivelu: Great, Will watch out for it. ---- 2019-02-12 21:14:26 UTC - Chris DiGiovanni: I'm trying to run the simulation tools on my cluster is in Kubernetes. On my desktop I spin up the simulation client, and then spin up the simulation controller. I then give the trade command. I get a bunch of errors of the client trying to contact the broker but notice it is using podIP to connect. I don't see anywhere to configure the broker-url using these tools? ---- 2019-02-12 21:17:47 UTC - Chris DiGiovanni: Am I missing something? ---- 2019-02-12 21:47:28 UTC - Ali Ahmed: what simulation tools are these ? ---- 2019-02-12 21:49:27 UTC - Jon Bock: @Ali Ahmed: <https://pulsar.apache.org/docs/latest/project/SimulationTools/> ---- 2019-02-12 21:51:04 UTC - Ali Ahmed: ```pulsar-perf simulation-client --port <listen port> --service-url <pulsar service url>``` ---- 2019-02-12 21:51:12 UTC - Ali Ahmed: are you using this command ? ---- 2019-02-12 22:25:19 UTC - Ryan Samo: Hey guys, we created a new cluster but initialized the cluster metadata with a typo in the broker service url. All works fine unless you try to hit the cluster from a WebSocket client, then it complains of the typo. We updated the metadata but it still complains. Is there a way to fix something like this? Thanks! ---- 2019-02-12 22:27:20 UTC - Ryan Samo: Java clients don’t seem to care. We basically had <https://broker.comm> instead of <https://broker.com> ---- 2019-02-12 22:43:23 UTC - David Kjerrumgaard: Did you restart the brokers after you updated the metadata? ---- 2019-02-12 22:49:42 UTC - Chris DiGiovanni: That command to start the client, and another to start the controller ---- 2019-02-13 00:43:08 UTC - Vincent Ngan: Yes, I have to put an adapter inside a legacy system which is still running on JDK 1.6 to communicate with Pulsar. The only option I have is to use the WebSocket client interface because the Java Pulsar client library requires JDK 1.8. ---- 2019-02-13 00:51:44 UTC - Vincent Ngan: Fortunately I found a easy way to do it by using a new JVM language called Kotlin. Kotlin requires only JDK 1.6 but provides a lot of new language features such as functional programming, type inference, concise syntax, null safety etc. Kotlin has a very nice framework called Ktor which provides a rich set of web application libraries including WebSocket client. ---- 2019-02-13 01:01:59 UTC - Vincent Ngan: BTW, I have become a Kotlin advocate, and highly recommend you consider using it in your future projects. For information about Kotlin, see <https://kotlinlang.org/> ---- 2019-02-13 01:30:01 UTC - Ali Ahmed: the ```--service-url``` parameter should be fine to pass the broker url ---- 2019-02-13 02:22:15 UTC - Ryan Samo: @David Kjerrumgaard yes I sure did, still no luck. I even tried stopping the bookies, brokers, and zookeepers. Then deleted all the zookeeper data directories, and then reinitialized the cluster metadata, but it still remembers the typo. I guess I’m just wondering where it keeps that metadata stored so that I can wipe it out. It’s a new cluster so no worries on loosing anything. ---- 2019-02-13 02:22:49 UTC - Ryan Samo: Also deleted the bookie data directories ---- 2019-02-13 02:23:17 UTC - David Kjerrumgaard: Wow, you really wanted it deleted :smiley: ---- 2019-02-13 02:23:25 UTC - Ryan Samo: Haha yup! ---- 2019-02-13 02:23:53 UTC - Matteo Merli: Did you try the use the bk tool to clean the bookie? `bookeeper shell bookieformat` ---- 2019-02-13 02:24:59 UTC - Ryan Samo: Nope I did not, I will sure try this tomorrow! Is that in the docs somewhere where I might have missed it? ---- 2019-02-13 02:25:39 UTC - Matteo Merli: Uhm. I’m not sure where that is documented :) ---- 2019-02-13 02:26:00 UTC - Matteo Merli: Though it should be somewhere in the BK docs :) ---- 2019-02-13 02:28:12 UTC - Ryan Samo: Yup found it! <https://bookkeeper.apache.org/docs/4.5.0/reference/cli/> ---- 2019-02-13 02:28:41 UTC - Ryan Samo: So the initialize metadata command saves into the bookies then? ---- 2019-02-13 02:36:01 UTC - JinJing: @JinJing has joined the channel ---- 2019-02-13 04:49:10 UTC - bossbaby: I used kerberos for the bookkeeper and when running broker, I received the following error: ``` 11:45:01.991 [bookkeeper-ml-workers-OrderedExecutor-0-0] ERROR org.apache.bookkeeper.mledger.impl.ManagedLedgerImpl - [public/default/persistent/test] Failed to open ledger 79962: Attempted to access ledger using the wrong password ``` So what is the password here? ---- 2019-02-13 05:02:09 UTC - jia zhai: @bossbaby this is because you meet UnauthorizedAccessException ``` case Code.UnauthorizedAccessException: return "Attempted to access ledger using the wrong password"; ``` ---- 2019-02-13 05:02:33 UTC - jia zhai: Seems the config between broker and bookie not set right. ---- 2019-02-13 05:03:11 UTC - jia zhai: broker is working as bookkeeper client in bookkeeper kerberos config ---- 2019-02-13 05:10:56 UTC - jia zhai: But currently, it seem not be able to do the config for broker. ---- 2019-02-13 05:11:03 UTC - jia zhai: How do you config this? ---- 2019-02-13 05:11:54 UTC - Matteo Merli: @jia zhai +1 : jia zhai ---- 2019-02-13 05:11:55 UTC - Matteo Merli: <https://github.com/apache/pulsar/blob/master/conf/broker.conf#L329> ---- 2019-02-13 05:14:44 UTC - jia zhai: Oh, I see. @Matteo Merli Thanks a lot ---- 2019-02-13 05:17:31 UTC - jia zhai: Yes, seems we only need this config. krb5 and jaas config files is provided by -Dxxx. ---- 2019-02-13 06:39:47 UTC - bossbaby: so the client should use the same bookie keytab or create a new keytab for the broker? ---- 2019-02-13 06:51:05 UTC - bossbaby: if i use the same bookie keytab to run broker, error occurred when pulsar-client c++ connected and producer message: ---- 2019-02-13 07:38:44 UTC - bossbaby: ---- 2019-02-13 08:04:33 UTC - jia zhai: @bossbaby have you tried successfully config kerberos for bookie and bookie-client? ---- 2019-02-13 08:06:42 UTC - jia zhai: client and bookie config should be different. ---- 2019-02-13 08:09:33 UTC - bossbaby: Is the bookie-client a broker? ----
