GitHub user jaikiran opened a pull request:
https://github.com/apache/kafka/pull/111
KAFKA-2405 Don't kill the JVM on session establishment failure
As noted in the JIRA https://issues.apache.org/jira/browse/KAFKA-2405
currently the KafkaHealthCheck causes the JVM to termina
GitHub user jaikiran opened a pull request:
https://github.com/apache/kafka/pull/138
Log the real exception which triggered a reconnect
The commit here improves the logging in SimpleConsumer to log the real
reason why a reconnect was attempted. Relates to
https://issues.apache.org
GitHub user jaikiran opened a pull request:
https://github.com/apache/kafka/pull/1825
MINOR: Reduce the log level when the peer isn't authenticated but is using
SSL
The commit here changes the log level of a log message from WARN to DEBUG.
As noted in the mail discussion
GitHub user jaikiran opened a pull request:
https://github.com/apache/kafka/pull/1837
MINOR: Update the README.md to include a note about GRADLE_USER_HOME
Trying to build the source and publish it to internal Maven repo, I ran
into an issue that I explain in the mailing list
GitHub user jaikiran opened a pull request:
https://github.com/apache/kafka/pull/3043
KAFKA-5232 Fix Log.parseTopicPartitionName to take into account dot
character in topic names of deleted topics
The commit here contains a fix and testcase for the issue reported in
https
GitHub user jaikiran opened a pull request:
https://github.com/apache/kafka/pull/3050
(trunk) KAFKA-5232 Fix Log.parseTopicPartitionName to take into account dot
character in topic names of deleted topics
The commit here contains a fix and a test case for the issue reported in
Github user jaikiran closed the pull request at:
https://github.com/apache/kafka/pull/3043
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
? That way any new RC release
would mean just changing the version number in our dependencies and
being sure it pulls in the right version.
[1]
https://repository.apache.org/content/groups/staging/org/apache/kafka/kafka_2.12/1.0.0/
-Jaikiran
On 24/10/17 6:30 AM, Guozhang Wang wrote:
H
a (and SSL), so I thought I will bring this to their
notice.
[1] https://jaitechwriteups.blogspot.com/2017/10/kafka-with-openssl.html
-Jaikiran
I haven't yet had a chance to try out Java 9, but that's definitely on
my TODO list, maybe sometime this weekend.
Thanks for pointing me to KAFKA-2561. I had missed that.
-Jaikiran
On 30/10/17 4:17 PM, Mickael Maison wrote:
Thanks for sharing, very interesting read.
Did you get a
Congratulations Kafka team on the release. Happy to see Kafka reach this
milestone. It has been a pleasure using Kafka and also interacting with
the Kafka team.
-Jaikiran
On 01/11/17 7:57 PM, Guozhang Wang wrote:
The Apache Kafka community is pleased to announce the release for Apache
Kafka
Congratulations Onur!
-Jaikiran
On 06/11/17 10:54 PM, Jun Rao wrote:
Hi, everyone,
The PMC of Apache Kafka is pleased to announce a new Kafka committer Onur
Karaman.
Onur's most significant work is the improvement of Kafka controller, which
is the brain of a Kafka cluster. Over tim
and
releases?
By the way, why June 2018? :)
-Jaikiran
On 09/11/17 3:14 PM, Ismael Juma wrote:
Hi all,
I'm starting this discussion early because of the potential impact.
Kafka 1.0.0 was just released and the focus was on achieving the original
project vision in terms of features pro
in Java
9, *WildFly OpenSSL still out-performs the one shipped in JRE*.
Like in the Java 8 runs, all default configs and settings were used, not
just for Kafka but even the JRE (i.e. no explicit choice of cipher suites).
[1] https://jaitechwriteups.blogspot.com/2017/10/kafka-with-openssl.html
Adding the Kafka dev list to cc, hoping they would answer this question.
-Jaikiran
On Friday 10 June 2016 11:18 AM, Jaikiran Pai wrote:
We are using 0.9.0.1 of Kafka server and (Java) clients. Our (Java)
consumers are assigned to dynamic runtime generated groups i.e. the
consumer group name is
help in quickly submitting the changes.
-Jaikiran
On Thursday 30 April 2015 06:42 PM, Ismael Juma wrote:
Hi all,
Kafka currently uses a combination of Review Board and JIRA for
contributions and code review. In my opinion, this makes contribution and
code review a bit harder than it has to be.
I
here and let me know if they run into any issues.
Thanks,
Jaikiran Pai
at we default the log directory to data/ in the kafka installation
> > directory and possibly encourage storing kafka data under var/ if it must
> > be overridden for production, by changing this commented out value to
> > /var/kafka-logs?
This has now been addressed to
this patch
to incorporate Neha's review comments. This is now ready to be reviewed again.
- Jaikiran Pai
On May 18, 2015, 4:42 a.m., Jaikiran Pai wrote:
>
> ---
> This is an automatically generated e-mail. To reply,
notes the
next version as 0.8.3-SNAPSHOT.
-Jaikiran
ea6d165d8e5c3146d2c65e8ad1a513308334bf6f
Diff: https://reviews.apache.org/r/34394/diff/
Testing
---
Thanks,
Jaikiran Pai
27;ve also checked that shutting down
Kafka first, when zookeeper is still up, works fine too.
Thanks,
Jaikiran Pai
es to reconnect to zoookeeper for a maximum of
5 seconds before cleanly shutting down). I've also checked that shutting down
Kafka first, when zookeeper is still up, works fine too.
Thanks,
Jaikiran Pai
---
Thanks,
Jaikiran Pai
There's also this one https://reviews.apache.org/r/34697/ for
https://issues.apache.org/jira/browse/KAFKA-2221 but it's only been up
since a couple of days and is a fairly minor one.
-Jaikiran
Hi Joe,
Comments inline.
On Friday 29 May 2015 12:15 PM, Joe Stein wrote:
see below
On Fri, May 29, 2015 at 2:25 AM, Jaikiran Pai
wrote:
Could someone please look at these few review requests and let me know if
any changes are needed:
https://reviews.apache.org/r/34394/ related to
https
and
> > written up in a KIP. We can't hard code values that folks won't understand
> > without some clear information about why it is 5000
Ok. I'll read through the KIP process and create a new one.
- Jaikiran
---
y.state.change.logger=false
Is it intentional to have this at TRACE level for the default shipped
config instead of having something like INFO or maybe DEBUG?
-Jaikiran
On Tuesday 13 December 2016 03:02 PM, Jaikiran Pai wrote:
log4j.logger.kafka.controller=*TRACE,* controllerAppender
log4j.additivity.kafka.controller=false
log4j.logger.state.change.logger=*TRACE*, stateChangeAppender
log4j.additivity.state.change.logger=false
Is it intentional to have
ACE level which contribute to this, before filing
a JIRA.
-Jaikiran
Ismael
On Tue, Dec 13, 2016 at 9:32 AM, Jaikiran Pai
wrote:
We happened to run into a disk space usage issue with Kafka 0.10.0.1 (the
version we are using) on one of our production setups this morning. Turns
out (log4
topic creation issue. In our case we are explicitly invoking the create
topic operation via the Java API.
-Jaikiran
for this, I'll send
a note on what approach I settled on.
-Jaikiran
On Friday 24 February 2017 12:08 PM, James Cheng wrote:
On Feb 23, 2017, at 10:03 PM, Jaikiran Pai wrote:
(Re)posting this from the user mailing list to dev mailing list, hoping for
some inputs from the Kafka dev
onsFor, although looked promising, won't work
out. So, I'm going to go back to the metadata.max.age.ms and fiddle with
it a bit to keep it at a low value (was trying to avoid this, since this
then is applicable throughout the lifetime of that consumer).
[1] https://gist.github.com/jaiki
Jaikiran,
What about
1) create topic
2) create consumer1 and do consumer1.partitionsFor() until it succeeds
3) close consumer1
4) create consumer2 and do consumer2.subscribe()
-James
An update on this. This workaround has worked out fine and our initial
tests so far show that it gets us
Thank you for pointing me to that JIRA. It indeed is the same issue we
discussed in this thread. I'll keep a watch on that JIRA for the code to
be merged.
-Jaikiran
On Thursday 02 March 2017 07:11 PM, Rajini Sivaram wrote:
This issue is being addressed in KAFKA-4631. See
of a
jira.ini file, during patch submission
Diffs (updated)
-
kafka-patch-review.py b7f132f9d210b8648859ab8f9c89f30ec128ab38
Diff: https://reviews.apache.org/r/29756/diff/
Testing
---
Thanks,
Jaikiran Pai
b7f132f9d210b8648859ab8f9c89f30ec128ab38
Diff: https://reviews.apache.org/r/29756/diff/
Testing
---
Thanks,
Jaikiran Pai
A user :nehanarkhede
> > JIRA password :
> > Failed to login to the JIRA instance
> > 'JIRA' object has no attribute 'current_user'
> >
> > Maybe a different version of the jira package we use renamed the user
> > field ?
>
use there isn't really any real server around)
final Future futureAck = producer.send(product);
Any pointers to existing tests?
-Jaikiran
use there isn't really any real server around)
final Future futureAck = producer.send(product);
Any pointers to existing tests?
-Jaikiran
ot(TM) Server VM (build 24.71-b01, mixed mode)
Should there be a check in the script, before adding this option?
-Jaikiran
On Wednesday 14 January 2015 10:08 PM, Jun Rao wrote:
+ users mailing list. It would be great if people can test this out and
report any blocker issues.
Thanks,
Jun
On Tue,
ntegration/kafka/api/ProducerFailureHandlingTest.scala
420a1dd30264c72704cc383a4161034c7922177d
Diff: https://reviews.apache.org/r/30013/diff/
Testing
---
Thanks,
Jaikiran Pai
timed out the metadata update wait during the
producer.send. I increased the metadata fetch timeout specifically for
that producer in that test method and was able to get past this. I've
sent a patch here https://reviews.apache.org/r/30013/
-Jaikiran
On Sunday 18 January 2015 12:30 AM, Mani
ntegration/kafka/api/ProducerFailureHandlingTest.scala
420a1dd30264c72704cc383a4161034c7922177d
Diff: https://reviews.apache.org/r/30026/diff/
Testing
---
Thanks,
Jaikiran Pai
ption which is causing the
test to fail. I've opened a review request with a proposed fix
https://reviews.apache.org/r/30026/diff/
-Jaikiran
On Sunday 18 January 2015 09:37 PM, Harsha wrote:
Jaikiran,
I can't reproduce the failure of the ProdcuerFailureHandlingTest.
I
update this patch (and run the test) with the change you suggest. Thanks
Jun Rao!
- Jaikiran
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/30026/#review68620
/src/test/scala/integration/kafka/api/ProducerFailureHandlingTest.scala
420a1dd30264c72704cc383a4161034c7922177d
Diff: https://reviews.apache.org/r/30026/diff/
Testing
---
Thanks,
Jaikiran Pai
t seems it's simpler to just change the defaultOffsetPartition in the
> > broker config to 1. The test will run faster that way.
>
> Jaikiran Pai wrote:
> That sounds good too. I don't yet have enough knowledge of the code to be
> sure it wouldn't introduce other issues, so wen
if(callback != null) {
- callback(response)
+ if (callback != null) {
+callback(response)
+ }
}
}
However can this really be considered a fix or would this just be hiding
the real issue and would there be something more that will have to be
done in this case? I'm on trunk FWIW.
-Jaikiran
/
Testing
---
Thanks,
Jaikiran Pai
JIRA created https://issues.apache.org/jira/browse/KAFKA-1883 and patch
submitted for review. Thanks Guozhang.
-Jaikiran
On Tuesday 20 January 2015 05:53 AM, Guozhang Wang wrote:
Hi Jaikiran,
This is a real bug, could you file a JIRA?
As for the fix, I think your proposal would be the right
/diff/
Testing
---
Thanks,
Jaikiran Pai
eWaitTime
PASSED
`
`
./gradlew core:test --tests
kafka.api.test.ProducerFailureHandlingTest.testCannotSendToInternalTopic
kafka.api.test.ProducerFailureHandlingTest > testCannotSendToInternalTopic
PASSED
`
Thanks,
Jaikiran Pai
; testMetadataUpdateWaitTime
PASSED
```
```
./gradlew core:test --tests
kafka.api.test.ProducerFailureHandlingTest.testCannotSendToInternalTopic
kafka.api.test.ProducerFailureHandlingTest > testCannotSendToInternalTopic
PASSED
```
Thanks,
Jaikiran Pai
so haven't added any new tests.
Thanks,
Jaikiran Pai
<https://reviews.apache.org/r/27799/#comment113741>
Hi Jay,
I think doing this unmuteAll in a finally block might be a good idea, since
that way we don't end up with a muted selected when/if something goes wrong
during that polling.
- Jaikiran Pai
On Jan. 21, 2015, 4:4
> On Jan. 22, 2015, 3:14 a.m., Jaikiran Pai wrote:
> > clients/src/main/java/org/apache/kafka/clients/NetworkClient.java, line 253
> > <https://reviews.apache.org/r/27799/diff/4/?file=828376#file828376line253>
> >
> > Hi Jay,
> >
> > I
nSocketNIO.java:361)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
-Jaikiran
``
```
./gradlew core:test --tests
kafka.api.test.ProducerFailureHandlingTest.testCannotSendToInternalTopic
kafka.api.test.ProducerFailureHandlingTest > testCannotSendToInternalTopic
PASSED
```
Thanks,
Jaikiran Pai
x27;t added any new tests.
Thanks,
Jaikiran Pai
x27;t added any new tests.
Thanks,
Jaikiran Pai
ete,
> > but then after deleting schedule another one.
> >
> > Should the scheduler action be inside the try block so it only occurs
> > if the rename succeeds?
Sorry, I missed a return statement in the catch block. Fixe
WaitTime
PASSED
```
```
./gradlew core:test --tests
kafka.api.test.ProducerFailureHandlingTest.testCannotSendToInternalTopic
kafka.api.test.ProducerFailureHandlingTest > testCannotSendToInternalTopic
PASSED
```
Thanks,
Jaikiran Pai
> On Jan. 24, 2015, 7:05 a.m., Manikumar Reddy O wrote:
> > Can you update the README.md document
Sure. I just did and have updated this patch.
- Jaikiran
---
This is an automatically generated e-mail. To reply, vis
le and file channel for read/write
final File originalLogFile = new
File("/home/jaikiran/deleteme/test.log"); // change this path relevantly
if you plan to run it
final FileChannel fileChannel = new
RandomAccessFile(originalLogFile, "rw").getChannel();
where like
KAFKA_INSTALL_FOLDER/data/kafka-logs/ folder. Is that something we
should do?
-Jaikiran
On Monday 26 January 2015 12:23 AM, Jay Kreps wrote:
Hmm, but I don't think tmp gets cleaned while the server is running...
The reason for using tmp was because we don't know which directory they
will u
x27;t added any new tests.
Thanks,
Jaikiran Pai
tils.Utils$.swallow(Utils.scala:45)
at kafka.server.KafkaServer.shutdown(KafkaServer.scala:269)
at
kafka.server.KafkaServerStartable.shutdown(KafkaServerStartable.scala:42)
at kafka.Kafka$$anon$1.run(Kafka.scala:42)
-Jaikiran
On Monday 26 January 2015 05:46 AM, Neha Narkhede wr
82dce80d553957d8b5776a9e140c346d4e07f766
Diff: https://reviews.apache.org/r/30403/diff/
Testing
---
Thanks,
Jaikiran Pai
his change on a Windows OS and would appreciate if
someone can test this there and let me know if they run into any issues.
Thanks,
Jaikiran Pai
I have created a JIRA for this proposed change
https://issues.apache.org/jira/browse/KAFKA-1906 and uploaded a patch
for review https://reviews.apache.org/r/30403/
-Jaikiran
On Tuesday 27 January 2015 02:36 AM, Jay Kreps wrote:
Having a relative path and keeping data under /data in the kafka
and if someone started the Kafka server,
while currently being in /home/me/ folder:
```
[/home/me]$ /opt/kafka/bin/kafka-server-start.sh
/opt/kafka/config/server.properties
```
then the Kafka data logs will end up being in a folder relative to /home/me
instead of the /op
ME}/data
> > may be enough?
> >
> > overriding configuration from server.properties in code can be very
> > unintuitive.
That sounds a good idea. I wasn't aware of the --override option. I'll give
that a try and if it works then
ME}/data
> > may be enough?
> >
> > overriding configuration from server.properties in code can be very
> > unintuitive.
>
> Jaikiran Pai wrote:
> That sounds a good idea. I wasn't aware of the --override option. I'll
> give that a try and if it works t
ME}/data
> > may be enough?
> >
> > overriding configuration from server.properties in code can be very
> > unintuitive.
>
> Jaikiran Pai wrote:
> That sounds a good idea. I wasn't aware of the --override option. I'll
> give that a try and if it works
://reviews.apache.org/r/30477/diff/
Testing
---
Thanks,
Jaikiran Pai
) ZkClient
which for now allows time outs to be optionally specified for certain
operations. I intentionally haven't forced the use of this new
KafkaZkClient all over the code and instead for now have just used it in
the KafkaServer.
Does this patch look like something worth using?
-Jaikira
install and run to be
straightforward without having to change/add configurations. Having
sensible defaults helps in development environments and in getting
started. IMO, this param belongs to that category.
-Jaikiran
On Thursday 29 January 2015 08:00 PM, Jeff Holoman wrote:
Maybe I'm i
this potential improvement
to them. I have no objection to contributing this or something similar
to Zookeeper directly. I think I should be able to bring this up in the
Zookeeper dev forum, sometime soon in the next few weekends.
-Jaikiran
On Sunday 01 February 2015 11:40 AM, Gwen Shapira wrote
k about it (filing an issue doesn't
seem right to ask this question). So I'll get in touch with the repo
owner and see what his plans for the project are.
-Jaikiran
On Monday 02 February 2015 11:33 PM, Gwen Shapira wrote:
I did!
Thanks for clarifying :)
The client that is part of Zooke
y
did indicate that the project could be released after this change is merged.
-Jaikiran
On Tuesday 03 February 2015 09:03 AM, Jaikiran Pai wrote:
Thanks for pointing to that repo!
I just had a look at it and it appears that the project isn't much
active (going by the lack of a
Yes, that's the plan :)
-Jaikiran
On Wednesday 04 February 2015 12:33 AM, Gwen Shapira wrote:
So I think the current plan is:
1. Add timeout in zkclient
2. Ask zkclient to release new version (we need it for few other things too)
3. Rebase on new zkclient
4. Fix this jira and the few o
lling to release a new version if/when we
need one.
-Jaikiran
On Wednesday 04 February 2015 12:33 AM, Gwen Shapira wrote:
So I think the current plan is:
1. Add timeout in zkclient
2. Ask zkclient to release new version (we need it for few other things too)
3. Rebase on new zkclient
4. Fix this
the JIRAs that we
expect to be resolved are indeed resolved and then asking the ZkClient
team to do a release might be something that we should do. If this
sounds good and if someone can point me to the exact JIRAs that need to
be verified, then I can look into this. Let me know.
-Jaikiran
O
e
application which reproduces this easily on a 0.9.0.1 setup here
https://gist.github.com/jaikiran/45e9ce510c259267b28821b84105a25a.
Let me know if you need more details about this.
-Jaikiran
a/clients/NetworkClient.java
and I think we should be fine if we bumped up the log level of that
class in our logging config to be ERROR, since it doesn't log anything
real useful below that level from that class.
-Jaikiran
On Monday 16 May 2016 02:30 PM, Rajini Sivaram wrote
On Monday 16 May 2016 04:52 PM, Rajini Sivaram wrote:
Hi Jaikiran,
1) If you delete a topic with no outstanding sends, you will see one WARN
log entry and the topic is immediately removed from the metadata. If you
delete a topic with outstanding sends, you will see a sequence of WARN logs
until
/7/docs/api/java/net/NetworkInterface.html#getInterfaceAddresses%28%29
after looking up the NetworkInterface by name
http://docs.oracle.com/javase/7/docs/api/java/net/NetworkInterface.html#getByName%28java.lang.String%29
Is this something that could be added as an enhancement?
-Jaikiran
lease instead?
-Jaikiran
On Thursday 02 July 2015 06:27 AM, Ashish Singh wrote:
Hey Guys,
In last KIP hangout, we decided on following path for deprecating
ConsumerOffsetChecker.
1. Add deprecation warning to the tool for one release. In this case, the
warning will be added in 0.9.0.
2. Drop it compl
Congratulations Gwen.
Gwen has been very helpful in various places (blogs, user mailing lists)
which has helped me (and I'm sure many others) in using Kafka and even
contributing patches. Very well deserved promotion.
-Jaikiran
On Tuesday 07 July 2015 07:36 AM, Guozhang Wang wrote:
Con
Thanks for explaining, Ewen.
-Jaikiran
On Thursday 02 July 2015 02:03 PM, Ewen Cheslack-Postava wrote:
Jaikiran,
After the last KIP discussion, I've been tasked with proposing a policy to
address general rules across all public interfaces including APIs, configs,
metrics, and command
the latest?
-Jaikiran
Recently there was a discussion that 0.8.2.2 will be released soon to
fix the critical issue with compression. Is that still the plan or has
that been shelved?
-Jaikiran
On Tuesday 01 September 2015 09:51 AM, Aditya Auradkar wrote:
createTopic should also be fine unless you try to create the same topic
concurrently.
Just to be clear - that would imply the AdminUtils _cannot_ be
considered thread-safe, isn't it?
-Jaikiran
On Mon, Aug 31, 2015 at 3:
ill end up being useful if only the config
name is logged without the value.
Can I add this as a JIRA and provide a patch?
-Jaikiran
Any opinion about this proposed change?
-Jaikiran
On Tuesday 16 August 2016 02:28 PM, Jaikiran Pai wrote:
We are using 0.9.0.1 of Kafka (Java) libraries for our Kafka consumers
and producers. In one of our consumers, our consumer config had a SSL
specific property which ended up being used
Thanks for the inputs.
I think it's fine if Kafka selectively logs values for certain configs
and masks others (the passwords). So from what I understand, this looks
more like a bug where it unintentionally ended up logging these values.
Do you want me to file a JIRA for this?
-Jai
Created https://issues.apache.org/jira/browse/KAFKA-4056.
-Jaikiran
On Wednesday 17 August 2016 06:28 PM, Ismael Juma wrote:
Yes, please file a JIRA.
Thanks,
Ismael
On Wed, Aug 17, 2016 at 1:46 PM, Jaikiran Pai
wrote:
Thanks for the inputs.
I think it's fine if Kafka selectively
n issues. I suspect the value being passed over the channel is
incorrect.
Of course this exception is triggered by a user config error but given
that ends up in a (almost unclear) OOM and causing the JVM to go in a
bad state, is there a way the Kafka Java library can handle this better?
Should I file a JIRA for this? I can share a sample application on
github, if it helps.
-Jaikiran
Hi Rajini,
Just filed a JIRA as suggested
https://issues.apache.org/jira/browse/KAFKA-4090. More comments inline.
On Friday 26 August 2016 07:53 PM, Rajini Sivaram wrote:
Jaikiran,
At the moment there is no client-side configuration parameter to restrict
the maximum request size on clients
1 - 100 of 246 matches
Mail list logo
