2020-08-09 21:34:43 UTC - alex kurtser: Hello Is it the right way to run brokers in the debug log level? PULSAR_EXTRA_OPTS = -Dpulsar.log.root.level=debug ---- 2020-08-10 01:02:23 UTC - Sijie Guo: Can you create a github issue for it? ---- 2020-08-10 01:03:12 UTC - Sijie Guo: What operating system you used to run Pulsar? ---- 2020-08-10 01:06:45 UTC - Sijie Guo: Did you check the node application code? It is possible that your node application doesn’t send acks when processing some of the messages. ---- 2020-08-10 01:09:10 UTC - Sijie Guo: PULSAR_LOG_LEVEL=debug bin/pulsar ---- 2020-08-10 01:09:17 UTC - Sijie Guo: You can do something like this ---- 2020-08-10 03:06:20 UTC - Galen Suen: How can I send message with key use python client? ---- 2020-08-10 03:07:13 UTC - Galen Suen: ---- 2020-08-10 03:25:27 UTC - Rob: Yes, it always acknowledges the message ---- 2020-08-10 03:29:17 UTC - Rob: Also, it's unclear why Pulsar doesn't resend the messages ---- 2020-08-10 06:33:59 UTC - charles: @Arek R. ^^ ---- 2020-08-10 07:05:25 UTC - Arek R.: Thanks @charles definitely I'll check it just switched temporary to kafka ---- 2020-08-10 07:10:17 UTC - Arek R.: pulsar + streamnative connector + spark streaming+join on streams is it working for you ? Not sure if it's about my query or sth under the hood ---- 2020-08-10 07:11:39 UTC - harley albert: in server i use centos bro, do you have a solution for my issue? please share, I really hope ---- 2020-08-10 07:40:27 UTC - xue: Function problem description:
1. The log of function is directly input into Kafka, then into elk, and then in Java- instance.jar Kafka's appender is added to java_instance_log4j2.xml file, instantiation of Kafka fails. 2. If the broker cluster fails abnormally, delete Function, the process is killed, but the subscription relationship of the consumed topic is still in use and has not been deleted. From the pulsar manager, the subscription relationship is displayed abnormally. For example, if the subscription type is empty and the backlog has a value, if you delete it with pulsar admin, it will prompt that the subscription relationship exists in the pulsar process in use. Actually, the process is no longer available. 3. Function worker load balancing. After create function, add a functions worker, and the load will not be concurrent to the newly started functions worker. pulsar 2.5.2 ---- 2020-08-10 08:06:12 UTC - alex kurtser: Thanks ---- 2020-08-10 08:22:59 UTC - hnail: @hnail has joined the channel ----
