Sounds good, yup!
/***
Joe Stein
Founder, Principal Consultant
Big Data Open Source Security LLC
http://www.stealth.ly
Twitter: @allthingshadoop
/
On Oct 24, 2013, at 1:12 PM, Jun Rao wrote:
> At this mom
At this moment, we have resolved all jiras that we intend to fix in 0.8.0
final.
Joe,
Would you like to drive the 0.8.0 final release again?
Thanks,
Jun
On Mon, Oct 21, 2013 at 8:53 PM, Jun Rao wrote:
> Hi, Everyone,
>
> At this moment, we have only one remaining jira (KAFKA-1097) that we p
Hi, Everyone,
At this moment, we have only one remaining jira (KAFKA-1097) that we plan
to fix in 0.8. After that, we can cut the final 0.8 release.
Thanks,
Jun
On Mon, Oct 7, 2013 at 5:33 PM, Jun Rao wrote:
> Hi, Everyone,
>
> I made another pass of the remaining jiras that we plan to fix i
The fetch thread uses multi-fetch. Have you looked at
https://cwiki.apache.org/confluence/display/KAFKA/FAQ#FAQ-Whymessagesaredelayedinmyconsumer%3F,
which may be related to your issue.
Thanks,
Jun
On Sun, Oct 20, 2013 at 2:48 AM, Jason Rosenberg wrote:
> Ok,
>
> So here's an outline of what
Ok,
So here's an outline of what I think seems to have happened.
I have a consumer, that uses a filter to consume a large number of topics
(e.g. several hundred). Each topic has only a single partition.
It normally has no trouble keeping up processing all messages on all
topics. However, we h
I'll try to, next time it hangs!
On Sat, Oct 19, 2013 at 4:04 PM, Neha Narkhede wrote:
> Can you send around a thread dump of the halted consumer process?
>
>
>
> On Sat, Oct 19, 2013 at 12:16 PM, Jason Rosenberg
> wrote:
>
> > The latest HEAD does seem to solve one issue, where a new topic bei
Can you send around a thread dump of the halted consumer process?
On Sat, Oct 19, 2013 at 12:16 PM, Jason Rosenberg wrote:
> The latest HEAD does seem to solve one issue, where a new topic being
> created after the consumer is started, would not be consumed.
>
> But the bigger issue is that we
The latest HEAD does seem to solve one issue, where a new topic being
created after the consumer is started, would not be consumed.
But the bigger issue is that we have a couple different consumers both
consuming the same set of topics (under different groupids), and hanging
after a while (both ha
Yes, 0.8 will be released from the HEAD of the 0.8 branch. Is the problem
with consuming new topics or topics whose partitions are increased? If so,
see KAFKA-1030 and KAFKA-1075.
Thanks,
Jun
On Fri, Oct 18, 2013 at 4:03 PM, Jason Rosenberg wrote:
> Will the 0.8 release come from the HEAD of
Will the 0.8 release come from the HEAD of the 0.8 branch? I'd like to
experiment with it, to see if it solves some of the issues I'm seeing, with
consumers refusing to consume new messages. We've been using the beta1
version.
I remember mention there was a Jira issues along these lines, which w
I uploaded a patch against trunk which also fixes KAFKA-1036, the other
knows windows issue. Review appreciated. Should be an easy one.
https://issues.apache.org/jira/browse/KAFKA-1008
-Jay
On Wed, Oct 9, 2013 at 8:56 AM, Jun Rao wrote:
> KAFKA-1008 has been checked into the 0.8 branch and ne
Sounds good to me too.
-Jay
On Wed, Oct 9, 2013 at 8:56 AM, Jun Rao wrote:
> KAFKA-1008 has been checked into the 0.8 branch and needs to be manually
> double-committed to trunk. To avoid merging problems, I suggest that for
> all future changes in the 0.8 branch, we double commit them to trun
Sounds good to me.
Thanks,
Neha
On Wed, Oct 9, 2013 at 8:56 AM, Jun Rao wrote:
> KAFKA-1008 has been checked into the 0.8 branch and needs to be manually
> double-committed to trunk. To avoid merging problems, I suggest that for
> all future changes in the 0.8 branch, we double commit them to
KAFKA-1008 has been checked into the 0.8 branch and needs to be manually
double-committed to trunk. To avoid merging problems, I suggest that for
all future changes in the 0.8 branch, we double commit them to trunk. Any
objections?
Thanks,
Jun
On Mon, Oct 7, 2013 at 5:33 PM, Jun Rao wrote:
>
Jun,
KAFKA-1018 should be fixed in 0.8 final I can post a patch or review.
+1 on the list for whats left
On Mon, Oct 7, 2013 at 8:33 PM, Jun Rao wrote:
> Hi, Everyone,
>
> I made another pass of the remaining jiras that we plan to fix in the 0.8
> final release.
>
>
> https://issues.apache.org
Hi, Everyone,
I made another pass of the remaining jiras that we plan to fix in the 0.8
final release.
https://issues.apache.org/jira/browse/KAFKA-954?jql=project%20%3D%20KAFKA%20AND%20fixVersion%20%3D%20%220.8%22%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20
Based on the list above, we may be able to clear up the remaining jiras in
roughly 3 weeks, so we can plan for a final release in a month or so. We
would appreciate contributions and patches to close out the remaining jiras.
Thanks
Neha
On Thu, Sep 19, 2013 at 4:15 AM, Haithem Jarraya wrote:
>
Hi Jun,
any updates on this, there is a final release is planned soon?
Thanks,
Haithem
On 13 Sep 2013, at 17:18, Jun Rao wrote:
> Hi, Everyone,
>
> We have been stabilizing the 0.8 branch since the beta1 release. I think we
> are getting close to an 0.8 final release. I made an initial list
Hi, Everyone,
We have been stabilizing the 0.8 branch since the beta1 release. I think we
are getting close to an 0.8 final release. I made an initial list of the
remaining jiras that should be fixed in 0.8.
https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20fixVersion%20%3D
19 matches
Mail list logo
