2020-03-15 17:18:17 UTC - Charles: @Charles has joined the channel ---- 2020-03-15 20:37:37 UTC - Vince Pergolizzi: Does a client need to do anything additional during the connect/topic lookup handshake if connecting via a Pulsar proxy service URL (couldn’t see anything in the docs) ---- 2020-03-16 04:45:30 UTC - Prasad Reddy: I Managed to set up pulsar 2.5.0-3 on kubernetes and doing some benchmark tests and noticed that Broker DIRECT MEMORY is hitting MAX and causing for broker performance issues and disconnect frequently the below are the exceptions from broker logs.
WARN org.apache.pulsar.broker.loadbalance.impl.LeastLongTermMessageRate - Broker 172.16.92.20:8080 is overloaded: CPU: 4.0314054%, MEMORY: 18.252926%, *DIRECT MEMORY: 91.015625%*, BANDWIDTH IN: 0.20474307%, BANDWIDTH OUT: 0.3635624% WARN org.apache.pulsar.broker.loadbalance.impl.OverloadShedder - HIGH USAGE WARNING : Sole namespace bundle public/default/0xa0000000_0xb0000000 is overloading broker 172.16.92.20:8080. No Load Shedding will be done on this broker. ----
