justinrixx commented on issue #403:
URL:
https://github.com/apache/pulsar-client-go/issues/403#issuecomment-2226402482
>No. You should either use `Nack` or `ReconsumeLater` to redelivery those
messages.
Is this the recommendation for handling errors from `Ack`? (processing is
alread
frankjkelly commented on issue #403:
URL:
https://github.com/apache/pulsar-client-go/issues/403#issuecomment-2162968162
> > pity there's no way to have a `defer` block where I could inspect the
message ack state and ensure it is acked or nacked. I probably just need to
rewrite my code to h
RobertIndie commented on issue #403:
URL:
https://github.com/apache/pulsar-client-go/issues/403#issuecomment-2162530359
> pity there's no way to have a `defer` block where I could inspect the
message ack state and ensure it is acked or nacked. I probably just need to
rewrite my code to hav
frankjkelly commented on issue #403:
URL:
https://github.com/apache/pulsar-client-go/issues/403#issuecomment-2152456295
> > if my various paths through the code don't result in an Ack or Nack
> > will the message be redelivered to existing consumers - it sounds like
the answer is no.
RobertIndie commented on issue #403:
URL:
https://github.com/apache/pulsar-client-go/issues/403#issuecomment-2151354334
> I was talking about this Ack Timeout in the Java Consumer
https://github.com/codelipenghui/incubator-pulsar/blob/a7f9670402a54b99fbc7ac9717a837092cf444cf/pulsar-clien
frankjkelly commented on issue #403:
URL:
https://github.com/apache/pulsar-client-go/issues/403#issuecomment-2147857955
> > For our Java services the message is automagically redelivered after a
fixed delay to (one of the shared) existing consumers regardless of consumer
connection/reconne
RobertIndie commented on issue #403:
URL:
https://github.com/apache/pulsar-client-go/issues/403#issuecomment-2146368018
> For our Java services the message is automagically redelivered after a
fixed delay to (one of the shared) existing consumers regardless of consumer
connection/reconnect
frankjkelly commented on issue #403:
URL:
https://github.com/apache/pulsar-client-go/issues/403#issuecomment-2139437499
> There is no delay in this case. When the consumer reconnects, the broker
immediately delivers unacked messages.
Ah maybe I was unclear - the Golang consumer remai
RobertIndie commented on issue #403:
URL:
https://github.com/apache/pulsar-client-go/issues/403#issuecomment-2139378469
> Thanks for the clarification but I presume there is some delay between the
initial message delivery and redelivery (due to lack of an ack). If so is that
defined by the
frankjkelly commented on issue #403:
URL:
https://github.com/apache/pulsar-client-go/issues/403#issuecomment-2139340100
> > What if consumer crashed after consuming message but before ack/nack the
message? Does broker redeliver in that case?
>
> Yes. The broker will redeliver those m
RobertIndie commented on issue #403:
URL:
https://github.com/apache/pulsar-client-go/issues/403#issuecomment-2139238541
> What if consumer crashed after consuming message but before ack/nack the
message? Does broker redeliver in that case?
Yes. The broker will redeliver those message
frankjkelly commented on issue #403:
URL:
https://github.com/apache/pulsar-client-go/issues/403#issuecomment-2129543290
> > This was left out on purpose from the Go client lib. Ack timeout was the
wrong solution we initially applied. Later we introduced negative Acks which
are better suite
sagarrohankar-bsft commented on issue #403:
URL:
https://github.com/apache/pulsar-client-go/issues/403#issuecomment-1884395575
> This was left out on purpose from the Go client lib. Ack timeout was the
wrong solution we initially applied. Later we introduced negative Acks which
are better
13 matches
Mail list logo
