; would be better but how would that look like
in a console producer ☺
or maybe simply a commit every n seconds.
BTW. Is there maybe any plan to implement the exactly once semantics in to the
mirrormaker?
BR,
Marcin
On 03.08.17, 21:01, "Apurva Mehta" wrote:
Ismael r
he creation of the
internal transaction topic ?
BR,
Marcin
We have kafka behind NAT with *only one broker*.
Let say we have internal (A) and external (B) network.
When we try to reach the broker from external network (we use
bootstrap.servers parameter set to B address) then what is obvious the
broker responds with internal network's address (A) which is
Kafka
Client classes to use SafeUtils instead of Utils everything was working
again. Alternatively you could patch Utils class in lz4 library and
backport changeRange method from SafeUtils to Utils. Not very elegant and
safe but it works.
Regards,
Marcin
On 21 March 2016 at 21:17, Dana Powers
n this!
>
> Can you comment on how this compares to Confluent's REST proxy?
>
> On Sat, May 16, 2015 at 12:01 AM, Marcin Kuthan
> wrote:
>
>> Hi Everyone
>>
>> Hermes is an asynchronous message broker built on top of Kafka. It
>> provides reliable, fault
ter? We did not encounter Kafka limitations for max number of
topics in our pub/sub scenarios.
> On May 16, 2015 8:02 AM, "Marcin Kuthan" wrote:
>
>> Hi Everyone
>>
>> Hermes is an asynchronous message broker built on top of Kafka. It
>> provides reliable, fa
consumer, redeliver messages, keep eye on
throughput limits etc.
Feedback and comments are welcome, you can find Hermes documentation at:
http://hermes-pubsub.readthedocs.org/en/latest/index.html
Hermes is published under Apache Licence:
https://github.com/allegro/hermes
Best Regards,
Marcin
I am running on 0.8.1.1 and I thought that the partition reassignment tools
can do this job. Just was not sure if this is the best way to do this.
I will try this out in stage env first and will perform the same in prod.
Thanks,
marcin
On Mon, Aug 25, 2014 at 7:23 PM, Joe Stein wrote
actually lower the
number of replicas as well, if I just simply make sure that given
topic/partition was only elected 3 times versus 4?
Thanks for your insight,
Marcin
supported by recent browsers -
http://stackoverflow.com/a/9632363/313516
Marcin
--
http://blog.solidsoft.info/ - Working code is not enough
gt;
> As for your issue, not sure what happened. Do you see any ZK session
> expirations in the broker log?
>
> Thanks,
>
> Jun
>
>
> On Thu, Apr 10, 2014 at 7:34 PM, Marcin Michalski >wrote:
>
> > I see that the state-change logs have warning messages of this
time?
Thanks,
Martin
On Wed, Apr 9, 2014 at 8:38 PM, Jun Rao wrote:
> Was there any error in the controller and the state-change logs?
>
> Thanks,
>
> Jun
>
>
> On Wed, Apr 9, 2014 at 11:18 AM, Marcin Michalski >wrote:
>
> > Hi, has anyone upgraded their ka
Hi, has anyone upgraded their kafka from 0.8.0 to 0.8.1 successfully one
broker at a time on a live cluster?
I am seeing strange behaviors where many of my kafka topics become unusable
(by both consumers and producers). When that happens, I see lots of errors
in the server logs that look like this
13 matches
Mail list logo