Somethings for you to check
>
> On Thu, May 5, 2016 at 7:37 AM, John Bickerstaff <j...@johnbickerstaff.com
> >
> wrote:
>
> > kafka_2.10-0.8.2.2
> >
> > Thanks
> >
> > On Wed, May 4, 2016 at 9:42 PM, Salman Ahmed <ahmed.sal...@gmail.com>
> >
This may or may not help. I found it to be a clever workaround for some of
the limitations in the 8.x version of the high level consumer... I ended
up writing code that "waited" a lot because I couldn't be sure how quickly
Kafka would respond...
Nothing ever took minutes however... the waits
kafka_2.10-0.8.2.2
Thanks
On Wed, May 4, 2016 at 9:42 PM, Salman Ahmed <ahmed.sal...@gmail.com> wrote:
> Which version of Kafka are you on?
> On Wed, May 4, 2016 at 4:54 PM John Bickerstaff <j...@johnbickerstaff.com>
> wrote:
>
> > Hi,
> >
> > I
I get the following error when trying to print out the message list on the
command line using: kafka-console-consumer.sh --zookeeper
192.168.56.5:2181/kafka --topic statdxSolrXmlDocs --from-beginning
[2016-05-04 19:55:03,690] WARN
Hi,
I've been working with Kafka a lot recently and have the log retention set
to over two years.
Today, as I was trying some things I happened to have the log running in
another window and on two different VMs, Kafka decided to delete all my log
messages, thus losing the entire topic's worth of
be
> confidential and/or legally privileged.
> If it has come to you in error you must take no action based on it, nor
> must you copy or show it to anyone; please delete/destroy and inform the
> sender immediately.
>
>
>
> On Wednesday, 4 May 2016 at 23:04, John Bicke
Hi,
I have what is probably an edge use case. I'd like to back up a single
Kafka instance such that I can recreate a new server, drop Kafka in, drop
the data in, start Kafka -- and have all my data ready to go again for
consumers.
Is such a thing done? Does anyone have any experience trying
Hmmm... I don't know for sure, but any chance a re-boot of Zookeeper would
help?
Is your topic still in /admin/delete_topics? (On Zookeeper I mean)
Also, how important is it to know what happened as opposed to just getting
to a runnable state again?
In other words, what time/effort will it
ot;auto.offset.reset" to "smallest". (this will direct the consumer to look
> for smallest offset if it doesnt find one in zookeeper)
>
> On Wed, Feb 17, 2016 at 1:06 PM, John Bickerstaff <
> j...@johnbickerstaff.com>
> wrote:
>
> > Hmmm... more info.
> >
n oversimplification for purposes of the
introduction - I get that...)
Feel free to comment or not - I'm going to keep digging into it as best I
can - any clarifications will be gratefully accepted...
On Wed, Feb 17, 2016 at 1:50 PM, John Bickerstaff <j...@johnbickerstaff.com>
wrote:
t to 0, i'll read everything. If you set the offset to 10,
> I'll read the second and third messages, and so on.
>
> see more here:
>
> http://research.microsoft.com/en-us/um/people/srikanth/netdb11/netdb11papers/netdb11-final12.pdf
> and here: http://kafka.apache.org/document
*Use Case: Disaster Recovery & Re-indexing SOLR*
I'm using Kafka to hold messages from a service that prepares "documents"
for SOLR.
A second micro service (a consumer) requests these messages, does any final
processing, and fires them into SOLR.
The whole thing is (in part) designed to be used
12 matches
Mail list logo
