You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/10/26 07:02:23 UTC
[GitHub] [pulsar-dotpulsar] amareshmad opened a new issue, #118: producer status evaluation before creating new producer
amareshmad opened a new issue, #118:
URL: https://github.com/apache/pulsar-dotpulsar/issues/118
Is there way to restrict/avoid producer creation for same topic for multiple instances.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-dotpulsar] blankensteiner commented on issue #118: producer status evaluation before creating new producer
Posted by GitBox <gi...@apache.org>.
blankensteiner commented on issue #118:
URL: https://github.com/apache/pulsar-dotpulsar/issues/118#issuecomment-1308616856
No, get the message, process it, and if successful when acknowledge.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-dotpulsar] blankensteiner commented on issue #118: producer status evaluation before creating new producer
Posted by GitBox <gi...@apache.org>.
blankensteiner commented on issue #118:
URL: https://github.com/apache/pulsar-dotpulsar/issues/118#issuecomment-1303304994
DotPulsar doesn't support batching on the producer side, only when reading/consuming.
Not sure how this is connected to your request? Did you have a look at the access modes?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-dotpulsar] amareshmad commented on issue #118: producer status evaluation before creating new producer
Posted by GitBox <gi...@apache.org>.
amareshmad commented on issue #118:
URL: https://github.com/apache/pulsar-dotpulsar/issues/118#issuecomment-1294556260
Thanks @blankensteiner. Consider now I have two different producers (for two different regions East & West and both are in connected status) and both are having same data, but I want to send only from one producer, if same data tries to send by another producer which was connected other region, it should not send. How to restrict this?
or
I have two producers for two different regions (East & West), if one fails, I have to send data to another (for this reason I have created two producers). if both are connected and sending same data to two different regions, will it affect/duplicate data at the consumer (consumer also active for two regions) of the produced data.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-dotpulsar] amareshmad commented on issue #118: producer status evaluation before creating new producer
Posted by GitBox <gi...@apache.org>.
amareshmad commented on issue #118:
URL: https://github.com/apache/pulsar-dotpulsar/issues/118#issuecomment-1308582730
@blankensteiner I have consumer received a message, acknowledged same but failed to process the message, I want ask broker to redeliver.
In case any failure in the acknowledged message to process, is there way we can ask broker to redeliver.
consumer.RedeliverUnacknowledgedMessages(messageId) => this is only for Unacknowledge.
what is the scenario for acknowledged to ask redeliver.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-dotpulsar] amareshmad commented on issue #118: producer status evaluation before creating new producer
Posted by GitBox <gi...@apache.org>.
amareshmad commented on issue #118:
URL: https://github.com/apache/pulsar-dotpulsar/issues/118#issuecomment-1299918122
Is there batch concept in C# dot pulsar producer by default? if there how to disable batch for producer.
We can see in server it is not able to parse some metadata. what they are telling in java they have batch concept and as to disable then they can parse batch info.
Similarly, for C# client, they could not parse metadata they are suspecting batch enable ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-dotpulsar] blankensteiner closed issue #118: producer status evaluation before creating new producer
Posted by GitBox <gi...@apache.org>.
blankensteiner closed issue #118: producer status evaluation before creating new producer
URL: https://github.com/apache/pulsar-dotpulsar/issues/118
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-dotpulsar] blankensteiner commented on issue #118: producer status evaluation before creating new producer
Posted by GitBox <gi...@apache.org>.
blankensteiner commented on issue #118:
URL: https://github.com/apache/pulsar-dotpulsar/issues/118#issuecomment-1291654656
Using the same producer name should fix that (only one will be allowed).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-dotpulsar] blankensteiner commented on issue #118: producer status evaluation before creating new producer
Posted by GitBox <gi...@apache.org>.
blankensteiner commented on issue #118:
URL: https://github.com/apache/pulsar-dotpulsar/issues/118#issuecomment-1294608852
Is this what you are looking for? https://pulsar.apache.org/docs/concepts-messaging/#access-mode
If not, then you need some kind of leader election (which is not in DotPulsar's scope) to find out who is allowed to run.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org