Usually for such a use case you'd have a physical load balancer box (F5,
etc.) in front of Kafka that would handle the SSL termination, but it
should be possible with NGINX as well:
https://docs.nginx.com/nginx/admin-guide/security-controls/terminating-ssl-tcp/
On Fri, 24 Aug 2018 at 18:35, Jack
You can try generating a random consumer group ID to ensure that no
existing offset is used.
On 20 January 2018 at 01:11, Matthias J. Sax wrote:
> That is not supported out-of-box.
>
> Configuration "auto.offset.reset" only triggers, if there are not
> committed offsets and there is KS config to
It is also used for rewinding consumer offsets.
On 19 January 2018 at 06:25, Matthias J. Sax wrote:
> The timestamp has many different purposes. As mentioned already, it used
> to expired data via retention time. It's also used for stream processing
> via Streams API. All processing is based on
You can add more instances of your application, to allow processing the
incoming data in parallel.
On 6 November 2017 at 20:11, Ranjit Kumar wrote:
> Hi,
>
> I am using kafka streaming and state store in my application using java but
> my application logic is taking more time (around 5 ms) to pi
ed Yu wrote:
> Can you update librdkafka and try again ?
> Thanks
> Original message ----From: Dan Markhasin
> Date: 10/25/17 11:26 PM (GMT-08:00) To: users@kafka.apache.org Subject:
> Re: Failure to reset consumer offsets for specific topics
> For beats (the topic
ed if it's pretty old and doesn't set timestamp on the messages it
produces.
On 26 October 2017 at 08:17, Elyahou Ittah wrote:
> Which driver is used yo produce these messages ?
>
> On Thu, Oct 26, 2017 at 8:14 AM, Dan Markhasin
> wrote:
>
> > Furthermore, when look
this
is where the broker takes the timestamps from, it explains why they are all
empty for data1_log.
On 26 October 2017 at 08:07, Dan Markhasin wrote:
> After a bit more checking it seems that Kafka isn't writing timestamps at
> all in the .timeindex file for the topics where offset re
ed yo produce these messages ?
>
> On Oct 26, 2017 07:11, "Dan Markhasin" wrote:
>
> > No, that flag doesn't affect which offsets are returned, only executes
> the
> > action (and resets the consumer to latest offset when used, regardless of
> > datetime val
-hans
>
> > On Oct 25, 2017, at 1:24 PM, Ted Yu wrote:
> >
> > I wonder if you have hit KAFKA-5600.
> >
> > Is it possible that you try out 0.11.0.1 ?
> >
> > Thanks
> >
> >> On Wed, Oct 25, 2017 at 1:15 PM, Dan Markhasin
> wrote:
ably check the broker log where data1_log is hosted - see if there is
> some clue.
>
> Thanks
>
> On Wed, Oct 25, 2017 at 12:11 PM, Dan Markhasin
> wrote:
>
> > I'm trying to use the kafka-consumer-groups.sh tool in order to rewind a
> > consumer group's off
I'm trying to use the kafka-consumer-groups.sh tool in order to rewind a
consumer group's offset, however it seems to be returning the latest offset
regarding of the requested offset.
You can see in the below example that two consecutive commands to reset the
offset to a specific point in time ret
If you run kafka-topics.sh --describe --topic __consumer_offsets, does it
show that all replicas are in sync?
On 23 August 2017 at 23:11, Murad Mamedov wrote:
> Hi David,
>
> Thanks for reply. However, I don't have problem with number of replicas. I
> have 3 brokers. And topics configured accord
Is your storm consumer set to auto.offset.reset="earliest"?
On 22 August 2017 at 10:05, Elyahou Ittah wrote:
> I checked the __consumer_offsets topic and here is an extraction from this
> log for the same consumer group, a specific topic (users) and specific
> partition (15):
>
> [storm_kafka_to
We are also collecting consumer group metrics from Kafka - we didn't want
to add extra unnecessary dependencies (such as burrow, which is also
overkill for what we need), so we just run a script every minute on the
brokers that parses the output of kafka-consumer-groups.sh and uploads it
to an http
14 matches
Mail list logo
