ll be open for 72 hours (ending at 1:00PM Monday, 08/21/2017).
> >
> > Please download the release candidate, check the hashes/signature, build
> it
> > and test it, and then please vote:
> >
> >
> > [ ] +1 approve
> >
> > [ ] +0 no opinion
> >
> > [ ] -1 disapprove (and reason why)
> >
> >
> > --
> > Fred Ji
> >
>
--
Thanks and regards
Chinmay Soman
> > > > > https://repository.apache.org/content/repositories/
> > > > orgapachesamza-1018
> > > > > > >
> > > > > > > Note that the binaries were built with JDK8 without incident.
> > > > > > >
> > > > > > > 26 issues were resolved for this release:
> > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20S
> > > > > > > AMZA%20AND%20fixVersion%20in%20(0.12%2C%200.12.0)%20AND%20st
> > > > > > > atus%20in%20(Resolved%2C%20Closed)
> > > > > > >
> > > > > > > The vote will be open for 72 hours (end in 6PM Thursday,
> > 02/09/2017
> > > > ).
> > > > > > >
> > > > > > > Please download the release candidate, check the
> > hashes/signature,
> > > > > build
> > > > > > it
> > > > > > > and test it, and then please vote:
> > > > > > >
> > > > > > >
> > > > > > > [ ] +1 approve
> > > > > > >
> > > > > > > [ ] +0 no opinion
> > > > > > >
> > > > > > > [ ] -1 disapprove (and reason why)
> > > > > > >
> > > > > > >
> > > > > > > +1 from my side for the release.
> > > > > > >
> > > > > > > Cheers!
> > > > > > >
> > > > > > > --
> > > > > > > Jagadish V,
> > > > > > > Graduate Student,
> > > > > > > Department of Computer Science,
> > > > > > > Stanford University
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Navina R.
> >
>
--
Thanks and regards
Chinmay Soman
on
>>> topic-partition
>>> > test3_a2_mobileDictClient_android_uid_imei-6, retrying (18 attempts
>>> > left). Error: NOT_LEADER_FOR_PARTITION
>>> > >> 2016-08-21 10:03:07 [WARN ](o.a.k.c.p.i.Sender :257)
>>> > Got error produce response with correlation id 490346 on
>>> topic-partition
>>> > test3_a2_mobileDictClient_android_uid_imei-3, retrying (16 attempts
>>> > left). Error: NOT_LEADER_FOR_PARTITION
>>> > >> 2016-08-21 10:03:07 [WARN ](o.a.k.c.p.i.Sender :257)
>>> > Got error produce response with correlation id 490346 on
>>> topic-partition
>>> > test3_a2_mobileDictClient_android_uid_imei-4, retrying (17 attempts
>>> > left). Error: NOT_LEADER_FOR_PARTITION
>>> > >> 2016-08-21 10:03:07 [WARN ](o.a.k.c.p.i.Sender :257)
>>> > Got error produce response with correlation id 490346 on
>>> topic-partition
>>> > test3_a2_mobileDictClient_android_uid_imei-6, retrying (17 attempts
>>> > left). Error: NOT_LEADER_FOR_PARTITION
>>> > >>
>>> > >> ...
>>> > >>
>>> > >> 2016-08-21 10:49:01 [WARN ](o.a.s.s.k.KafkaSystemProducer :66
>>> )
>>> > Retrying send messsage due to RetriableException -
>>> org.apache.kafka.common.
>>> > errors.NotLeaderForPartitionException: This server is not the leader
>>> for
>>> > that topic-partition.. Turn on debugging to get a full stack trace
>>> > >> 2016-08-21 10:49:11 [WARN ](o.a.s.s.k.KafkaSystemProducer :66
>>> )
>>> > Retrying send messsage due to RetriableException -
>>> org.apache.kafka.common.
>>> > errors.NotLeaderForPartitionException: This server is not the leader
>>> for
>>> > that topic-partition.. Turn on debugging to get a full stack trace
>>> > >> 2016-08-21 10:49:21 [WARN ](o.a.s.s.k.KafkaSystemProducer :66
>>> )
>>> > Retrying send messsage due to RetriableException -
>>> org.apache.kafka.common.
>>> > errors.NotLeaderForPartitionException: This server is not the leader
>>> for
>>> > that topic-partition.. Turn on debugging to get a full stack trace
>>> > >> 2016-08-21 10:49:31 [WARN ](o.a.s.s.k.KafkaSystemProducer :66
>>> )
>>> > Retrying send messsage due to RetriableException -
>>> org.apache.kafka.common.
>>> > errors.NotLeaderForPartitionException: This server is not the leader
>>> for
>>> > that topic-partition.. Turn on debugging to get a full stack trace
>>> > >> 2
>>> > >>
>>> > >> This happens since "rush hour" for new messages produced to kafka.
>>> May
>>> > be this is a bug of kafka / samza?
>>> > >>
>>> > >> kafka version: 0.10.0.0
>>> > >>
>>> > >> kafka config and part of paused log are attached.
>>> > >>
>>> > >>
>>> > >>
>>> > >
>>> > >
>>> > > --
>>> > > 李斯宁
>>> > >
>>> >
>>> >
>>> >
>>> > --
>>> > 李斯宁
>>> >
>>>
>>
>>
>>
>> --
>> 李斯宁
>>
>
>
>
> --
> 李斯宁
>
--
Thanks and regards
Chinmay Soman
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/45912/#review127925
---
Ship it!
- Chinmay Soman
On April 8, 2016, 11:40 p.m
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/45912/#review127702
---
Lets add a unit test for this.
- Chinmay Soman
On April 8
gt; >>>>>>> Hi, all,
> > >>>>>>>
> > >>>>>>> I want to start the discussion on our code review/commit process.
> > >>>>>>>
> > >>>>>>> I felt that our code review and check-in process is a little bit
> > >>>>>>> cumbersome:
> > >>>>>>> - developers need to create RBs and attach diff to JIRA
> > >>>>>>> - committers need to review RBs, dowload diff and apply, then
> push.
> > >>>>>>>
> > >>>>>>> It would be much lighter if we take the pull request only
> approach,
> > >>> as
> > >>>>>>> Kafka already converted to:
> > >>>>>>> - for the developers, the only thing needed is to open a pull
> > >>> request.
> > >>>>>>> - for committers, review and apply patch is from the same PR and
> > >>> merge
> > >>>>>> can
> > >>>>>>> be done directly on remote git repo.
> > >>>>>>>
> > >>>>>>> Of course, there might be some hookup scripts that we will need
> to
> > >>> link
> > >>>>>>> JIRA w/ pull request in github, which Kafka already does. Any
> > >>> comments
> > >>>>>> and
> > >>>>>>> feedbacks are welcome!
> > >>>>>>>
> > >>>>>>> Thanks!
> > >>>>>>>
> > >>>>>>> -Yi
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> --
> > >>>>> Navina R.
> > >>>>
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> Milinda Pathirage
> > >>>
> > >>> PhD Student | Research Assistant
> > >>> School of Informatics and Computing | Data to Insight Center
> > >>> Indiana University
> > >>>
> > >>> twitter: milindalakmal
> > >>> skype: milinda.pathirage
> > >>> blog: http://milinda.pathirage.org
> > >>>
> > >>
> > >
> > >
> > > --
> > > Sent from my iphone.
> >
> >
>
--
Thanks and regards
Chinmay Soman
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39032/#review117572
---
Ship it!
- Chinmay Soman
On Oct. 6, 2015, 12:44 a.m., Navina
t; It might be the mail list restriction. Could you try to my personal email
> (i.e. nickpa...@gmail.com)?
>
> On Thu, Jan 14, 2016 at 10:15 AM, Chinmay Soman >
> wrote:
>
> > It shows as attached in my sent email. That's weird.
> >
> > On Thu, Jan
It shows as attached in my sent email. That's weird.
On Thu, Jan 14, 2016 at 10:14 AM, Yi Pan wrote:
> Hi, Chinmay,
>
> Did you forget to attach? I did not see the attachment in your last email.
> Or is it due to the mail list restriction?
>
> On Thu, Jan 14, 2016 at
oved version in some time.
On Wed, Jan 6, 2016 at 11:31 AM, Yi Pan wrote:
> Hi, Chinmay,
>
> That's awesome! Could you share some design doc of this feature? We would
> love to have this feature in LinkedIn as well!
>
> -Yi
>
> On Wed, Jan 6, 2016 at 10:02 AM, Chinmay S
, Bae, Jae Hyeon wrote:
> Hi Samza devs and users
>
> I know this will be tricky in Samza because Samza Kafka consumer is not
> coordinated externally, but do you have any idea how to deploy samza jobs
> with zero downtime?
>
> Thank you
> Best, Jae
>
--
Thanks and regards
Chinmay Soman
Hey Jae , we've turned off log compaction because of issues seen earlier
with the log compaction thread on kafka. We're still on 0.8.2 so we cant
really turn it on.
Our best bet is to set retention to like 3 hours or something.
On Nov 4, 2015 12:18 AM, "Bae, Jae Hyeon" wrote:
> Also, I am using
said, the upcoming TTL
> > feature is not fully synchronized w/ the Kafka cleanup yet and is an
> > on-going work in the future. The recommendation is to use the TTL feature
> > and set the Kafka changelog to be time-retention based, w/ a retention
> time
> > longer than the RocksDB TTL to ensure no data loss.
> >
> > Hope the above answered your questions.
> >
> > Cheers!
> >
> > -Yi
> >
>
--
Thanks and regards
Chinmay Soman
lar problem? How it could be resolved?
>
> Best regards,
> Vladimir
>
> --
> Vladimir Lebedev
> w...@fastmail.fm
>
>
--
Thanks and regards
Chinmay Soman
upport
> > > > - Add CoordinatorStream and disable CheckpointManager
> > > > - Elasticsearch Producer
> > > > - Host affinity
> > > > And other 0.10.0 tickets:
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND%20status%20in%20(%22In%20Progress%22%2C%20Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%200.10.0
> > > >
> > > > I propose to cut a 0.10.0 release after we get the following issues
> > > > resolved:
> > > > - SAMZA-615: Migrate checkpoint from checkpoint topic to Coordinator
> > > stream
> > > > - SAMZA-617: YARN host affinity in Samza
> > > >
> > > > Thoughts?
> > > >
> > > > Thanks!
> > > >
> > > > -Yi
> > > >
> > >
> >
>
--
Thanks and regards
Chinmay Soman
AM, Tim Williams
> wrote:
>
> > I'm learning samza by the hello-samza project and notice the lack of
> > tests. Where's a good place to learn how folks are properly testing
> > things written with samza?
> >
> > Thanks,
> > --tim
> >
>
--
Thanks and regards
Chinmay Soman
causes SystemConsumers to hang
> >> >
> >> > SAMZA-616
> >> > Shutdown hook does not wait for container to finish
> >> >
> >> > SAMZA-658
> >> > Iterator.remove breaks caching layer
> >> >
> >> > SAMZA-662 / 686
> >> > Samza auto-creates changelog stream without sufficient partitions when
> >> > container number > 1
> >> >
> >> > I am proposing a release vote on the current 0.9.1 branch for these
> >>bug
> >> > fixes. Thoughts?
> >> >
> >> > -- Guozhang
> >> >
> >>
>
>
--
Thanks and regards
Chinmay Soman
.org/r/34011/#comment136061>
nit: Use final for snapshot ?
- Chinmay Soman
On May 21, 2015, 7:54 a.m., Luis De Pombo wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visi
the source as well (look at JmxReporter)
samza-core/src/main/java/org/apache/samza/metrics/reporter/SamzaGraphiteReporter.java
<https://reviews.apache.org/r/34011/#comment134083>
Include the source as well (look at JmxReporter)
for this and other metric names
- Chinmay Soman
Oh never mind - I forgot it being merged into core. Sorry for the noise.
On Wed, Apr 29, 2015 at 12:03 PM, Chinmay Soman
wrote:
> I don't see the serializers jar being published in Maven. Yan - know
> anything about this ?
>
> --
> Thanks and regards
>
> Chinmay
I don't see the serializers jar being published in Maven. Yan - know
anything about this ?
--
Thanks and regards
Chinmay Soman
ronmentConfigRewriter to modify config from environment
> > variable.
> > > >
> > > > What's the best way for us to add things like this? Do you want more
> > > > modules in the main project or should we just create some separate
> > > projects
> > > > on github?
> > > >
> > > > It would be good to get core extensions like these shared to be
> tested
> > > and
> > > > used by more people
> > > >
> > > > Thanks,
> > > > Dan
> > >
> >
>
--
Thanks and regards
Chinmay Soman
ey-to-partition
> > > assignment strategy, as well as the partition-to-node assignment
> > strategy.
> > > Optionally, a hook to access performance metrics could also be
> > implemented
> > > if throttling is deemed important (as described in the previous point).
> > > * Since the consumer process lives in a separate process, the
> system
> > > benefits from good isolation guarantees. The consumer process can be
> > capped
> > > to a low amount of heap, and its GC is inconsequential for the serving
> > > platform. It's also possible to bounce the consumer and data serving
> > > processes independently of each other, if need be.
> > >
> > > There are some more nuances and additional features which could be nice
> > to
> > > have, but that's the general idea.
> > >
> > >
> > > It seems to me like such system would be valuable, but I'm wondering
> what
> > > other people in the open-source community think, hence why I was
> > interested
> > > in starting this thread...
> > >
> > >
> > > Thanks for your feedback!
> > >
> > > -F
> > >
> >
>
--
Thanks and regards
Chinmay Soman
that seems quite a verbose way
> to
> > go about that?
> >
> > If Samza could use a prefix in the properties file then generate a topic
> > name for each task it would simplify using that. Maybe there's something
> > I'm missing from this?
> >
> > Thanks,
> > Dan
> >
>
--
Thanks and regards
Chinmay Soman
it's like RPC-over-Kafka
> solution which seems to me suboptimal.
>
> Any thoughts are welcome!
>
> --
> Vladimir Lebedev
> http://linkedin.com/in/vlebedev
>
>
--
Thanks and regards
Chinmay Soman
; > > >> > who
> > > >> > > > has
> > > >> > > > > > contributed to this release. We are very glad to see some
> > new
> > > >> > > > > contributors
> > > >> > > > > > in this release.
> > > >> > > > > >
> > > >> > > > > > The release candidate can be downloaded from here:
> > > >> > > > > >
> > > >> > > > > > http://people.apache.org/~yanfang/samza-0.9.0-rc0/
> > > >> > > > > >
> > > >> > > > > > The release candidate is signed with pgp key
> > CAC06239EA00BA80,
> > > >> > which
> > > >> > > is
> > > >> > > > > > included in the repository's KEYS file:
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > >
> > > >> > > >
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=blob_plain;f=KEYS;hb=6f5bafb6cd93934781161eb6b1868d11ea347c95
> > > >> > > > > >
> > > >> > > > > > and can also be found on keyservers:
> > > >> > > > > >
> > > >> > > > > >
> > > http://pgp.mit.edu/pks/lookup?op=get&search=0xCAC06239EA00BA80
> > > >> > > > > >
> > > >> > > > > > The git tag is release-0.9.0-rc0 and signed with the same
> > pgp
> > > >> key:
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > >
> > > >> > > >
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=1039f7ede6490f9420dcecd6adc7677b97e78bcf
> > > >> > > > > >
> > > >> > > > > > Test binaries have been published to Maven's staging
> > > repository,
> > > >> > and
> > > >> > > > are
> > > >> > > > > > available here:
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > >
> > > >> >
> > >
> https://repository.apache.org/content/repositories/orgapachesamza-1005/
> > > >> > > > > >
> > > >> > > > > > Note that the binaries were built with JDK6 without
> > incident.
> > > >> > > > > >
> > > >> > > > > > 95 issues were resolved for this release:
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > >
> > > >> > > >
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND%20fixVersion%20%3D%200.9.0%20AND%20status%20in%20(Resolved%2C%20Closed)
> > > >> > > > > >
> > > >> > > > > > The vote will be open for 72 hours ( end in 4:00pm Friday,
> > > >> > 03/27/2015
> > > >> > > > ).
> > > >> > > > > > Please download the release candidate, check the
> > > >> hashes/signature,
> > > >> > > > build
> > > >> > > > > it
> > > >> > > > > > and test it, and then please vote:
> > > >> > > > > >
> > > >> > > > > > [ ] +1 approve
> > > >> > > > > > [ ] +0 no opinion
> > > >> > > > > > [ ] -1 disapprove (and reason why)
> > > >> > > > > >
> > > >> > > > > > +1 from my side for the release.
> > > >> > > > > >
> > > >> > > > > > Fang, Yan
> > > >> > > > > > yanfang...@gmail.com
> > > >> > > > > > +1 (206) 849-4108
> > > >> > > > > >
> > > >> > > > >
> > > >> > > >
> > > >> > >
> > > >> >
> > > >>
> > >
> >
>
--
Thanks and regards
Chinmay Soman
t; matter of deserialization or is there any kind of metadata included that
> specifies the contest type?
>
> How do I enable the debug mode?
>
> Thanks,
>
> Jordi
>
> -Mensaje original-
> De: Chinmay Soman [mailto:chinmay.cere...@gmail.com]
> Enviad
> > This has been enough of a trial that I think I'll convert this into a
> very
> > simple sample project for the repo, if you guys are interested.
> >
> > Diff coming once I have it cleaned up into something less ugly.
> >
> > -Ash
> >
>
e inputting string and
outputting json. So you might have to set that explicitly.
On Mon, Mar 23, 2015 at 9:24 PM, Chinmay Soman
wrote:
> Since you're producing String data to 'myTopic', can you try setting the
> string serialization in your config
Timer(TimerUtils.scala:37)
> >> >>> >> at
> >> >>>org.apache.samza.container.RunLoop.updateTimer(RunLoop.scala:36)
> >> >>> >> at
> org.apache.samza.container.RunLoop.process(RunLoop.scala:79)
> >> >>> >>
t 5:13 PM, Ash W Matheson
> > wrote:
> >
> >> I'm assuming I have Jmx defined ... where would that get set?
> >>
> >> On Mon, Mar 23, 2015 at 5:08 PM, Chinmay Soman <
> chinmay.cere...@gmail.com
> >> > wrote:
> >>
> >>
015 at 5:08 PM, Chinmay Soman
> wrote:
>
> > Hey Ash,
> >
> > Can you see your job metrics (if you have the Jmx metrics defined) to see
> > if your job is actually doing anything ? My only guess at this point is
> the
> > process method is not being called bec
redacted:2181/
> >> > systems.kafka.consumer.auto.offset.reset=smallest
> >> > systems.kafka.producer.metadata.broker.list=redacted:9092
> >> >
> >> > and in the actual java file WikipediaParserStreamTask.java
> >> > public void process(IncomingMessageEnvelope envelope,
> MessageCollector
> >> > collector, TaskCoordinator coordinator) {
> >> >Map jsonObject = (Map)
> >> > envelope.getMessage();
> >> >WikipediaFeedEvent event = new WikipediaFeedEvent(jsonObject);
> >> >
> >> >try {
> >> >System.out.println(event.getRawEvent());
> >> >
> >> > And then following the compile/extract/run process outlined in the
> >> > hello-samza website.
> >> >
> >> > Any thoughts? I've looked online for any 'super simple' examples of
> >> > ingesting kafka in samza with very little success.
> >>
> >>
> >
>
--
Thanks and regards
Chinmay Soman
pache.samza.container.RunLoop.process(RunLoop.scala:100)
> at org.apache.samza.container.RunLoop.run(RunLoop.scala:83)
> at
> org.apache.samza.container.SamzaContainer.run(SamzaContainer.scala:549)
> at
> org.apache.samza.job.local.ThreadJob$$anon$1.run(ThreadJ
as I am streaming some syslogs to
> the "syslog" topic and I am testing "beste" with an internal application
> specifically designed. I am not sure about the kafka part.
>
> Thanks.
>
> Jordi
>
> -Mensaje original-
> De: Chinmay Soman [ma
in
> deploy/yarn/logs/userlogs (and subdirectories). I was assuming
> System.out.println(...) would stuff results into either application. any
> thoughts on that?
>
> On Sun, Mar 22, 2015 at 1:53 PM, Chinmay Soman
> wrote:
>
> > It says UnresolvedAddressException.
&g
scala:42)
>
> Is this a configuration issue? I tried changing the serializer to String
> but I has the same effect.
>
> Thanks,
>
>Jordi
>
> Jordi Blasi Uribarri
> Área I+D+i
>
> jbl...@nextel.es
> Oficina Bilbao
>
> [http://www.nextel.es/wp-content/uploads/Firma_Nextel_2014.png]
>
--
Thanks and regards
Chinmay Soman
hat into the 'hello-samza' and looking at
> >> http://samza.apache.org/learn/documentation/latest/jobs/logging.html
> >> leads me to believe that I have to do this in the base samza project
> (not
> >> hello-samza).
> >>
> >> On Sun
Can you please enable debug level logging and paste the log?
On Sun, Mar 22, 2015 at 11:28 AM, Ash W Matheson
wrote:
> No, it's behind some corporate stuff - I just redacted it so I could share
> it up.
>
> On Sun, Mar 22, 2015 at 11:17 AM, Chinmay Soman >
> wrote:
>
gt;
>
> On Sun, Mar 22, 2015 at 10:57 AM, Ash W Matheson
> wrote:
>
> > Yep, first thing I checked (got bitten by that earlier in the week with
> no
> > data actually in the topic).
> >
> > On Sun, Mar 22, 2015 at 10:56 AM, Chinmay Soman <
> chinmay.ce
a website.
>
> Any thoughts? I've looked online for any 'super simple' examples of
> ingesting kafka in samza with very little success.
>
--
Thanks and regards
Chinmay Soman
, Mar 18, 2015 at 6:16 PM, Chris Riccomini
wrote:
> Hey Chinmay,
>
> Cool, this is good feedback. I didn't think I was *that* crazy. :)
>
> Cheers,
> Chris
>
> On Wed, Mar 18, 2015 at 6:10 PM, Chinmay Soman
> wrote:
>
> > Thats what we're doing as
sure your join isn't
> screwed up. There'd need to be something somewhere to enforce that
> though.
>
--
Thanks and regards
Chinmay Soman
#x27;t interact with KV store from InitiableTask.init()
> > > > SAMZA-506
> > > > Shutdown container on SIGTERM
> > > > SAMZA-571
> > > > Add task interface suppress uncaught exceptions
> > > > SAMZA-576
> > > > Transient failures in
> > > > TestKafkaSystemAdmin.testShouldGetOldestNewestAndNextOffsets
> > > > SAMZA-505
> > > > CachedStore doesn't support Array keys well
> > > >
> > > > Here's what I propose:
> > > >
> > > > 1. Cut an 0.9.0 branch.
> > > > 2. Work on getting as many of these JIRAs done as possible.
> > > > 3. Target a release vote on the week of March 23.
> > > >
> > > > Thoughts?
> > > >
> > > > Cheers,
> > > > Chris
> > > >
> > >
> >
>
--
Thanks and regards
Chinmay Soman
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31290/#review73828
---
Ship it!
- Chinmay Soman
On Feb. 23, 2015, 12:23 a.m., Chris
er. IIRC,
> the cause was ZkClient blocking indefinitely.
>
> You may find this useful.
> https://issues.apache.org/jira/browse/KAFKA-1907
> http://mail-archives.apache.org/mod_mbox/kafka-dev/201501.mbox/browser
>
> Aditya
>
> ________
> F
hemeral znodes
> > of
> > > the previous run are still there in ZK.
> > >
> > > I imagine Kafka could have some logic to deal with that better when it
> > > gets fast-bounced... Alternatively, you may just have to wait a bit
> > before
> > > rest
down properly. This
issue goes away if I use the following sequence:
* bin/grid stop kafka
* bin/grid stop zookeeper (after like 5 seconds).
(and then start everything).
Has anyone else seen this ?
--
Thanks and regards
Chinmay Soman
for:
> >
> > https://issues.apache.org/jira/browse/INFRA-9055
> >
> > Cheers,
> > Chris
> >
>
--
Thanks and regards
Chinmay Soman
49 matches
Mail list logo
