2019-01-11 09:40:57 UTC - Sijie Guo: org.apache.bookkeeper.client.LedgerHandle - IncorrectParameterException on ledgerId:3 firstEntry:-1 lastEntry:-1 ---- 2019-01-11 09:41:24 UTC - Sijie Guo: this is an exception thrown from bookkeeper client. it seems that pulsar broker attempts to read entries from an invalid entry range. ---- 2019-01-11 09:42:54 UTC - Sijie Guo: which version of pulsar are you using? Can you describe the sequence you encountered this issue? ---- 2019-01-11 12:33:38 UTC - Samuel Sun: @Grant Wu :grinning: ---- 2019-01-11 15:09:23 UTC - Shalin: How is `numberOfEntriesSinceFirstNotAckedMessage` different from `msgBacklog` for a subscription? ---- 2019-01-11 15:23:46 UTC - Ezequiel Lovelle: afaik, `msgBacklog` are all messages created and not acked by consumer and `NumberOfEntriesSinceFirstNotAckedMessage` are num of messages from the first not acked message to current dispatching position (a subset of msgBacklog) ---- 2019-01-11 15:24:02 UTC - Karthik Palanivelu: I used Classic Load Balancer to route TCP to Proxy port ---- 2019-01-11 15:24:25 UTC - Karthik Palanivelu: It worked for me by keeping NodePort on Proxy ---- 2019-01-11 15:34:12 UTC - Shalin: ^ so these would values would be the same for an exclusive subscription? :thinking_face: ---- 2019-01-11 15:36:53 UTC - Shalin: Thanks @Karthik Palanivelu. Yea, thats what I ended up doing. I was just wary of handling a separate classic LB for for each service. ---- 2019-01-11 15:38:28 UTC - Shalin: Again, not a pulsar thing. Just wanted to manage it all using k8s or kops. ---- 2019-01-11 15:56:24 UTC - Ezequiel Lovelle: mmm I don't think that the type of the subscription is related, they are different things, one is to know how many messages are created and not being acked and the other one is to know the "distance" of messages between first not acked and current delivering position. Both are to debug behaviour of non acked messages from different perspectives ---- 2019-01-11 15:56:43 UTC - Grant Wu: Is there a particular reason why you want to create it explicitly? I think those types of topics are created automatically upon publishing or subscribing to them ---- 2019-01-11 16:14:03 UTC - Shalin: Does non-acked here mean a message that was read but not acked or not read at all? ---- 2019-01-11 16:15:10 UTC - Shalin: I have a subscription that has `msgBacklog` : 0 and `numberOfEntriesSinceFirstNotAckedMessage` : 1. Not sure how to interpret that with this definition. ---- 2019-01-11 16:26:52 UTC - Ezequiel: I think means both(read and not acked and not read at all), mmm strange maybe I was wrong ---- 2019-01-11 17:26:56 UTC - Victor Li: We are using 2.1.1. ---- 2019-01-11 17:29:34 UTC - Victor Li: This is a QA system, the system seems was deployed freshly and then this happened, not quite sure if anything else was done on it. ---- 2019-01-11 21:02:28 UTC - Victor Li: Just to let you know, we redeployed from scratch, the problem is gone. Not sure what happened before. ----
