2019-09-02 15:33:48 UTC - Poule: when is docker 2.4.1 scheduled to be released? pray : Ming Fang ---- 2019-09-02 15:44:02 UTC - Poule: is there a command to get all schemas of a topic ---- 2019-09-02 15:44:35 UTC - Poule: is it normal that I have a schema 0 and 2 but not 1. For it to skip numbers ok or not? ---- 2019-09-02 15:47:27 UTC - Ming Fang: Debugging networking depends on your network plugin since Kubernetes does not natively manage the network. But this tool can help identify a network problem quicker <https://github.com/bloomberg/goldpinger> ---- 2019-09-02 16:00:53 UTC - Poule: where can I find the logs for : ``` b'<html>\n<head>\n<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>\n<title>Error 500 Internal Server Error</title>\n</head>\n<body><h2>HTTP ERROR 500</h2>\n<p>Problem accessing /admin/v2/schemas/abc/def/x2/schema. Reason:\n<pre> Internal Server Error</pre></p><hr><a href="<http://eclipse.org/jetty>">Powered by Jetty:// 9.4.12.v20180830</a><hr/>\n\n</body>\n</html>\n' ``` in docker container? I looked for `logs`, `log`, `access.log`... just found an empty `logs/pulsar-standalone.log` ---- 2019-09-02 16:08:47 UTC - Chris Bartholomew: The logs are redirected to STDOUT and collected by docker. You can view them using ```docker logs <container-name>``` heart_eyes : Poule ---- 2019-09-02 16:28:37 UTC - Sijie Guo: it will be pushed when 2.4.1 is released. we almost have the votes and it should be released in 1~2 days heart_eyes : Poule, Sinan Bir ---- 2019-09-02 16:29:03 UTC - Sijie Guo: currently there is no such command. we added one for 2.5.0 heart_eyes : Poule ---- 2019-09-02 16:29:49 UTC - Sijie Guo: have you deleted schema before? ---- 2019-09-02 18:48:00 UTC - Poule: yes i think ---- 2019-09-02 18:51:00 UTC - Sijie Guo: if you deleted schema, version 1 is used for the deletion marker ---- 2019-09-02 18:54:57 UTC - Poule: the marker at 1 means 0 was deleted or it means 1 was deleted? ---- 2019-09-02 18:57:06 UTC - Poule: a deleted schema is not supposed to show with `schema get --version` right? ---- 2019-09-02 18:58:21 UTC - Poule: currently they always show even when they are but i think it's a bug in 2.4.0 ---- 2019-09-02 18:58:38 UTC - Poule: anyway i'll wait for 2.4.1. and continue learning ---- 2019-09-02 19:10:29 UTC - Sijie Guo: I think it will return the schema with a marker that says “deleted”. feel free to submit a pull request if you think the behavior is not correct. ---- 2019-09-02 19:48:31 UTC - Kim Christian Gaarder: In a java-client Consumer, when I seek using timestamp to a time that is after the publish-time of the very last message on a topic, is the consumer supposed to return the last message on the next receive() call or is it supposed to return null? I get the last message, but I kind of expected to get null. ---- 2019-09-02 23:08:52 UTC - Rowanto: @Matteo Merli sorry for the late reply. The 2242:21 is the offset from the latest message we get back from pulsar. We have a wrapper around pulsar, which saves offset, and on starting a consumer, do a manual seek using the saved offset. This is only working with the latest ledger. And as mentioned above, if the consumer lags for any reason, and ledger is closed, the manual seek will stop working with the above mentioned reason. ---- 2019-09-03 02:51:27 UTC - xue: I have a question, if I want to expand the capabilities of broker services, how do I operate? Start brokers for all nodes? How do all producers and consumers allocate these brokers, or do all producers and consumers connect only one broker? ---- 2019-09-03 04:03:51 UTC - sundar: @sundar has joined the channel ---- 2019-09-03 05:59:18 UTC - Ali Ahmed: first release of nodejs pulsar client is out <https://www.npmjs.com/package/pulsar-client> tada : Sijie Guo, Ali Ahmed, Karthik Ramasamy, Yuvaraj Loganathan ---- 2019-09-03 05:59:30 UTC - Ali Ahmed: it wraps over the c/c++ lib ---- 2019-09-03 06:44:15 UTC - Jianfeng Qiao: while useing pulsar go client, my app always hangs there because of the following stack: Thread 3 (Thread 0x7fd725fc6700 (LWP 29472)): #0 runtime.futex () at /data/fuxi_ci_workspace/1068811_cache/buildbox/go-1.11.1/src/runtime/sys_linux_amd64.s:532 #1 0x000000000043c95b in runtime.futexsleep (addr=0xc000044140, ns=-1, val=0) at /data/fuxi_ci_workspace/1068811_cache/buildbox/go-1.11.1/src/runtime/os_linux.go:46 #2 0x000000000041d762 in runtime.notesleep (n=0xc000044140) at /data/fuxi_ci_workspace/1068811_cache/buildbox/go-1.11.1/src/runtime/lock_futex.go:151 #3 0x000000000044543a in runtime.stoplockedm () at /data/fuxi_ci_workspace/1068811_cache/buildbox/go-1.11.1/src/runtime/proc.go:2165 #4 0x0000000000446b69 in runtime.schedule () at /data/fuxi_ci_workspace/1068811_cache/buildbox/go-1.11.1/src/runtime/proc.go:2565 #5 0x0000000000446cee in runtime.park_m (gp=0xc000000780) at /data/fuxi_ci_workspace/1068811_cache/buildbox/go-1.11.1/src/runtime/proc.go:2676 #6 0x000000000046c8db in runtime.mcall () at /data/fuxi_ci_workspace/1068811_cache/buildbox/go-1.11.1/src/runtime/asm_amd64.s:299 #7 0x00007fd725fc5160 in ?? () #8 0x00007fd72f39c740 in ?? () from /lib64/libc.so.6 #9 0x00007fd725fc51a0 in ?? () #10 0x000000000046e1de in runtime.cgocallback () at /data/fuxi_ci_workspace/1068811_cache/buildbox/go-1.11.1/src/runtime/asm_amd64.s:686 #11 0x0000000000843787 in _cgoexp_e85b1628361b_pulsarClientLoggerProxy (a=<optimized out>, ctxt=<optimized out>, n=<optimized out>) at _cgo_gotypes.go:1810 #12 0x0000000000577de7 in crosscall2 () at /data/fuxi_ci_workspace/1068811_cache/buildbox/go-1.11.1/src/runtime/cgo/asm_amd64.s:59 #13 0x0000000000a00424 in pulsarClientLoggerProxy (p0=637292632, p1=0x30 <Address 0x30 out of bounds>, p2=17, p3=0xc9ce74 "p\004\002 \220\031", p4=0x0) at _cgo_export.c:39 #14 0x00007fd72fd162e5 in PulsarCLogger::log (this=0x1ed12a0, level=pulsar::Logger::INFO, line=405, message=...) at /usr1/jevon/streaming/src/dmb/pulsar/pulsar-client-cpp/lib/c/c_ClientConfiguration.cc:84 #15 0x00007fd72fb3a7e6 in pulsar::ClientConnection::handleResolve (this=0x1e72340, err=..., endpointIterator=...) at /usr1/jevon/streaming/src/dmb/pulsar/pulsar-client-cpp/lib/ClientConnection.cc:405 [4:40 PM] Anyone run into this issue? ---- 2019-09-03 06:54:04 UTC - jia zhai: @Jianfeng Qiao How to reproduce this? ---- 2019-09-03 07:31:13 UTC - Jianfeng Qiao: My app just calls Subscribe() to create a consumer, then the app hangs there. ---- 2019-09-03 08:46:58 UTC - Raphael REYNAUD: @Raphael REYNAUD has joined the channel ---- 2019-09-03 09:03:42 UTC - jia zhai: @Jianfeng Qiao It would be help a lot if you could provide the details of how to reproduce it. ----
