cversion did change (incremented by 2) when I issue the delete command.
>From the logs on the conroller broker (also the leader for the topic), it
looks like the delete proceeds, and then the topic gets recreated
immediately (highlighted in yellow). It appears maybe it’s due to a
consumer client a
filed: https://issues.apache.org/jira/browse/KAFKA-1901
On Mon, Jan 26, 2015 at 1:27 AM, Jun Rao wrote:
> That maybe possible. Do you want to file a jira to track this?
>
> Thanks,
>
> Jun
>
> On Sun, Jan 25, 2015 at 9:56 PM, Jason Rosenberg wrote:
>
> > Or you could have your build generate a
That maybe possible. Do you want to file a jira to track this?
Thanks,
Jun
On Sun, Jan 25, 2015 at 9:56 PM, Jason Rosenberg wrote:
> Or you could have your build generate a static constant class from the
> build version.
>
> On Mon, Jan 26, 2015 at 12:06 AM, Jun Rao wrote:
>
> > The issue wit
Could you do a get on /admin/deleted_topics and see if its cversion changes
after issuing the delete topic command? This will tell us whether the
path /admin/deleted_topics//mytopic
is actually created or not. Anything in the controller log that indicates a
delete topic event is fired?
Thanks,
Ju
Or you could have your build generate a static constant class from the
build version.
On Mon, Jan 26, 2015 at 12:06 AM, Jun Rao wrote:
> The issue with embedding the version in the code is that you have to update
> the version in two places, the build script and the code.
>
> Thanks,
>
> Jun
>
>
yes
On Mon, Jan 26, 2015 at 12:18 AM, Jun Rao wrote:
> Do you have delete.topic.enable turned on in all brokers?
>
> Thanks,
>
> Jun
>
> On Sun, Jan 25, 2015 at 7:56 PM, Jason Rosenberg wrote:
>
> > So far, I have been unable to get delete topic to work, with release
> > candidate 2 for 0.8.2.
Do you have delete.topic.enable turned on in all brokers?
Thanks,
Jun
On Sun, Jan 25, 2015 at 7:56 PM, Jason Rosenberg wrote:
> So far, I have been unable to get delete topic to work, with release
> candidate 2 for 0.8.2.
>
> It worked ok when I ran it in the debugger locally, on a single node
The issue with embedding the version in the code is that you have to update
the version in two places, the build script and the code.
Thanks,
Jun
On Sun, Jan 25, 2015 at 7:05 PM, Jason Rosenberg wrote:
> I don't think it's really unusual for deployment environments to produce
> single shaded j
I have fixed this issue like this patch
https://reviews.apache.org/r/29755/diff/5/.
I find rename failure still happens:
server.log.2015-01-26-06:[2015-01-26 06:10:54,513] ERROR File rename
failed, forcefully deleting file (kafka.log.Log)
server.log.2015-01-26-06:[2015-01-26 06:10:54,600] ERROR F
So far, I have been unable to get delete topic to work, with release
candidate 2 for 0.8.2.
It worked ok when I ran it in the debugger locally, on a single node
instance. But when I run it in our staging environment, it is not
successfully even marking the topic for delete, for some reason.
I am
I don't think it's really unusual for deployment environments to produce
single shaded jars for an app. Thus, I'm wondering if we can't rethink
this here? E.g. just have a constant in code which states the version?
Rather than emit the confusing warning, especially for client apps?
Jason
On Fri
+1 (binding)
Verified keys, quick start, unit tests.
On Sat, Jan 24, 2015 at 4:26 PM, Joe Stein wrote:
> That makes sense, thanks!
>
> On Sat, Jan 24, 2015 at 7:00 PM, Jay Kreps wrote:
>
> > But I think the flaw in trying to guess what kind of serializer they will
> > use is when we get it wron
Also, what is the configuration for the servers? In particular it would be
good to know the retention and/or log compaction settings as those delete
files.
-Jay
On Sun, Jan 25, 2015 at 4:34 AM, Jaikiran Pai
wrote:
> Hi Yonghui,
>
> Do you still have this happening? If yes, can you tell us a bit
Hi Yonghui,
Do you still have this happening? If yes, can you tell us a bit more
about your setup? Is there something else that accesses or maybe
deleting these log files? For more context to this question, please read
the discussion related to this here
http://mail-archives.apache.org/mod_mb
Hi all,
I am currently working on logstash to mongodb.logstash's input
(producer) is kafka and output (consumer) is mongodb.It is worked fine for
past two days.Today it is not working and i got the following error.i
googled this error,still didnt find any correct solution.kindly help me to
15 matches
Mail list logo
