Re: Kafka 0.11.0 problem with transactions.

2017-08-04 Thread Bienek, Marcin
; 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

Kafka 0.11.0 problem with transactions.

2017-08-03 Thread Bienek, Marcin
he creation of the internal transaction topic ? BR, Marcin

Kafka behind NAT

2016-08-10 Thread 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

Re: Using lz4 compression

2016-03-22 Thread Marcin Kuthan
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

Re: [Announcement] Hermes - pub / sub broker built on top of Kafka

2015-05-18 Thread Marcin Kuthan
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

Re: [Announcement] Hermes - pub / sub broker built on top of Kafka

2015-05-18 Thread Marcin Kuthan
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

[Announcement] Hermes - pub / sub broker built on top of Kafka

2015-05-16 Thread Marcin Kuthan
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

Re: Migrating data from old brokers to new borkers question

2014-08-26 Thread Marcin Michalski
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

Migrating data from old brokers to new borkers question

2014-08-25 Thread Marcin Michalski
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

Switch Apache logo URL to HTTPS

2014-07-19 Thread Marcin Zajączkowski
supported by recent browsers - http://stackoverflow.com/a/9632363/313516 Marcin -- http://blog.solidsoft.info/ - Working code is not enough

Re: Upgrading from 0.8.0 to 0.8.1 one broker at a time issues

2014-04-11 Thread Marcin Michalski
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

Re: Upgrading from 0.8.0 to 0.8.1 one broker at a time issues

2014-04-10 Thread Marcin Michalski
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

Upgrading from 0.8.0 to 0.8.1 one broker at a time issues

2014-04-09 Thread Marcin Michalski
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