[jira] [Commented] (KAFKA-5232) Kafka broker fails to start if a topic containing dot in its name is marked for delete but hasn't been deleted during previous uptime

[ https://issues.apache.org/jira/browse/KAFKA-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009314#comment-16009314 ] jaikiran pai commented on KAFKA-5232: - One of the crude (but easy) way to reproduce th

[jira] [Updated] (KAFKA-5232) Kafka broker fails to start if a topic containing dot in its name is marked for delete but hasn't been deleted during previous uptime

[ https://issues.apache.org/jira/browse/KAFKA-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-5232: Status: Patch Available (was: Open) I just submitted a PR which contains a fix and includes a testc

[jira] [Updated] (KAFKA-5232) Kafka broker fails to start if a topic containing dot in its name is marked for delete but hasn't been deleted during previous uptime

[ https://issues.apache.org/jira/browse/KAFKA-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-5232: Description: We are using 0.10.2.0 (but this is reproducible even with 0.10.2.1 and latest upstream

[jira] [Created] (KAFKA-5232) Kafka broker fails to start if a topic containing dot in its name is marked for delete but hasn't been deleted during previous uptime

jaikiran pai created KAFKA-5232: --- Summary: Kafka broker fails to start if a topic containing dot in its name is marked for delete but hasn't been deleted during previous uptime Key: KAFKA-5232 URL: https://issues.ap

[jira] [Commented] (KAFKA-4631) Refresh consumer metadata more frequently for unknown subscribed topics

[ https://issues.apache.org/jira/browse/KAFKA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929414#comment-15929414 ] jaikiran pai commented on KAFKA-4631: - Thanks [~hachikuji], am glad this made it to 0.

[jira] [Commented] (KAFKA-4090) JVM runs into OOM if (Java) client uses a SSL port without setting the security protocol

[ https://issues.apache.org/jira/browse/KAFKA-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15439247#comment-15439247 ] jaikiran pai commented on KAFKA-4090: - Mailing list discussion is here https://www.ma

[jira] [Created] (KAFKA-4090) JVM runs into OOM if (Java) client uses a SSL port without setting the security protocol

jaikiran pai created KAFKA-4090: --- Summary: JVM runs into OOM if (Java) client uses a SSL port without setting the security protocol Key: KAFKA-4090 URL: https://issues.apache.org/jira/browse/KAFKA-4090

[jira] [Commented] (KAFKA-4056) Kafka logs values of sensitive configs like passwords

[ https://issues.apache.org/jira/browse/KAFKA-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426538#comment-15426538 ] jaikiran pai commented on KAFKA-4056: - [~mimaison], we ran into this on our system whe

[jira] [Created] (KAFKA-4056) Kafka logs values of sensitive configs like passwords

jaikiran pai created KAFKA-4056: --- Summary: Kafka logs values of sensitive configs like passwords Key: KAFKA-4056 URL: https://issues.apache.org/jira/browse/KAFKA-4056 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-493) High CPU usage on inactive server

[ https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257799#comment-15257799 ] jaikiran pai commented on KAFKA-493: FWIW - we have been seeing a similar issue in 0.8

[jira] [Updated] (KAFKA-2405) KafkaHealthCheck kills the JVM in handleSessionEstablishmentError

[ https://issues.apache.org/jira/browse/KAFKA-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-2405: Status: Patch Available (was: Open) Pull request sent https://github.com/apache/kafka/pull/111 >

[jira] [Created] (KAFKA-2405) KafkaHealthCheck kills the JVM in handleSessionEstablishmentError

jaikiran pai created KAFKA-2405: --- Summary: KafkaHealthCheck kills the JVM in handleSessionEstablishmentError Key: KAFKA-2405 URL: https://issues.apache.org/jira/browse/KAFKA-2405 Project: Kafka

[jira] [Updated] (KAFKA-2221) Log the entire cause which caused a reconnect in the SimpleConsumer

[ https://issues.apache.org/jira/browse/KAFKA-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-2221: Attachment: KAFKA-2221.patch > Log the entire cause which caused a reconnect in the SimpleConsumer >

[jira] [Updated] (KAFKA-2221) Log the entire cause which caused a reconnect in the SimpleConsumer

[ https://issues.apache.org/jira/browse/KAFKA-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-2221: Status: Patch Available (was: Open) > Log the entire cause which caused a reconnect in the SimpleCo

[jira] [Commented] (KAFKA-2221) Log the entire cause which caused a reconnect in the SimpleConsumer

[ https://issues.apache.org/jira/browse/KAFKA-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14560354#comment-14560354 ] jaikiran pai commented on KAFKA-2221: - Created reviewboard https://reviews.apache.org/

[jira] [Created] (KAFKA-2221) Log the entire cause which caused a reconnect in the SimpleConsumer

jaikiran pai created KAFKA-2221: --- Summary: Log the entire cause which caused a reconnect in the SimpleConsumer Key: KAFKA-2221 URL: https://issues.apache.org/jira/browse/KAFKA-2221 Project: Kafka

[jira] [Updated] (KAFKA-1907) ZkClient can block controlled shutdown indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1907: Attachment: KAFKA-1907_2015-05-25_09:18:14.patch > ZkClient can block controlled shutdown indefinite

[jira] [Commented] (KAFKA-1907) ZkClient can block controlled shutdown indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14557954#comment-14557954 ] jaikiran pai commented on KAFKA-1907: - Updated reviewboard https://reviews.apache.org/

[jira] [Commented] (KAFKA-2201) Open file handle leak

[ https://issues.apache.org/jira/browse/KAFKA-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555458#comment-14555458 ] jaikiran pai commented on KAFKA-2201: - This might be related http://mail-archives.apa

[jira] [Commented] (KAFKA-1907) ZkClient can block controlled shutdown indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549796#comment-14549796 ] jaikiran pai commented on KAFKA-1907: - Created reviewboard https://reviews.apache.org/

[jira] [Updated] (KAFKA-1907) ZkClient can block controlled shutdown indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1907: Attachment: KAFKA-1907.patch > ZkClient can block controlled shutdown indefinitely > ---

[jira] [Updated] (KAFKA-1907) ZkClient can block controlled shutdown indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1907: Status: Patch Available (was: In Progress) > ZkClient can block controlled shutdown indefinitely >

[jira] [Commented] (KAFKA-1906) Default the Kafka log directory to a relative path within the Kafka installation directory

[ https://issues.apache.org/jira/browse/KAFKA-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547526#comment-14547526 ] jaikiran pai commented on KAFKA-1906: - Updated reviewboard https://reviews.apache.org/

[jira] [Updated] (KAFKA-1906) Default the Kafka log directory to a relative path within the Kafka installation directory

[ https://issues.apache.org/jira/browse/KAFKA-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1906: Attachment: KAFKA-1906_2015-05-18_10:11:12.patch > Default the Kafka log directory to a relative pat

[jira] [Updated] (KAFKA-1906) Default the Kafka log directory to a relative path within the Kafka installation directory

[ https://issues.apache.org/jira/browse/KAFKA-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1906: Status: Patch Available (was: In Progress) > Default the Kafka log directory to a relative path wit

[jira] [Commented] (KAFKA-1907) ZkClient can block controlled shutdown indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332503#comment-14332503 ] jaikiran pai commented on KAFKA-1907: - Hi [~nehanarkhede], I submitted a patch for thi

[jira] [Updated] (KAFKA-1907) ZkClient can block controlled shutdown indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1907: Attachment: KAFKA-1907.patch > ZkClient can block controlled shutdown indefinitely > ---

[jira] [Updated] (KAFKA-1907) ZkClient can block controlled shutdown indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1907: Assignee: jaikiran pai Status: Patch Available (was: Open) > ZkClient can block controlled sh

[jira] [Commented] (KAFKA-1907) ZkClient can block controlled shutdown indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299832#comment-14299832 ] jaikiran pai commented on KAFKA-1907: - Created reviewboard https://reviews.apache.org/

[jira] [Updated] (KAFKA-1906) Default the Kafka log directory to a relative path within the Kafka installation directory

[ https://issues.apache.org/jira/browse/KAFKA-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1906: Attachment: KAFKA-1906.patch > Default the Kafka log directory to a relative path within the Kafka

[jira] [Commented] (KAFKA-1906) Default the Kafka log directory to a relative path within the Kafka installation directory

[ https://issues.apache.org/jira/browse/KAFKA-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14296435#comment-14296435 ] jaikiran pai commented on KAFKA-1906: - Created reviewboard https://reviews.apache.org/

[jira] [Updated] (KAFKA-1906) Default the Kafka log directory to a relative path within the Kafka installation directory

[ https://issues.apache.org/jira/browse/KAFKA-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1906: Status: Patch Available (was: Open) > Default the Kafka log directory to a relative path within the

[jira] [Created] (KAFKA-1906) Default the Kafka log directory to a relative path within the Kafka installation directory

jaikiran pai created KAFKA-1906: --- Summary: Default the Kafka log directory to a relative path within the Kafka installation directory Key: KAFKA-1906 URL: https://issues.apache.org/jira/browse/KAFKA-1906

[jira] [Commented] (KAFKA-1853) Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291855#comment-14291855 ] jaikiran pai commented on KAFKA-1853: - Updated reviewboard https://reviews.apache.org/

[jira] [Updated] (KAFKA-1853) Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1853: Attachment: KAFKA-1853_2015-01-26_19:41:33.patch > Unsuccessful suffix rename of expired LogSegment

[jira] [Commented] (KAFKA-1885) Allow test methods in "core" to be individually run from outside of the IDE

[ https://issues.apache.org/jira/browse/KAFKA-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290565#comment-14290565 ] jaikiran pai commented on KAFKA-1885: - Updated reviewboard https://reviews.apache.org/

[jira] [Updated] (KAFKA-1885) Allow test methods in "core" to be individually run from outside of the IDE

[ https://issues.apache.org/jira/browse/KAFKA-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1885: Attachment: KAFKA-1885_2015-01-24_17:21:59.patch > Allow test methods in "core" to be individually r

[jira] [Commented] (KAFKA-1853) Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290454#comment-14290454 ] jaikiran pai commented on KAFKA-1853: - Updated reviewboard https://reviews.apache.org/

[jira] [Updated] (KAFKA-1853) Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1853: Attachment: KAFKA-1853_2015-01-24_11:21:07.patch > Unsuccessful suffix rename of expired LogSegment

[jira] [Commented] (KAFKA-1869) Openning some random ports while running kafka service

[ https://issues.apache.org/jira/browse/KAFKA-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290445#comment-14290445 ] jaikiran pai commented on KAFKA-1869: - [~huqian] As [~omkreddy] noted, that ephemeral

[jira] [Updated] (KAFKA-1853) Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1853: Attachment: KAFKA-1853_2015-01-24_10:48:08.patch > Unsuccessful suffix rename of expired LogSegment

[jira] [Commented] (KAFKA-1853) Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290442#comment-14290442 ] jaikiran pai commented on KAFKA-1853: - Updated reviewboard https://reviews.apache.org/

[jira] [Updated] (KAFKA-1885) Allow test methods in "core" to be individually run from outside of the IDE

[ https://issues.apache.org/jira/browse/KAFKA-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1885: Attachment: KAFKA-1885_2015-01-24_10:42:46.patch > Allow test methods in "core" to be individually r

[jira] [Commented] (KAFKA-1885) Allow test methods in "core" to be individually run from outside of the IDE

[ https://issues.apache.org/jira/browse/KAFKA-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290441#comment-14290441 ] jaikiran pai commented on KAFKA-1885: - Updated reviewboard https://reviews.apache.org/

[jira] [Commented] (KAFKA-1853) Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283989#comment-14283989 ] jaikiran pai commented on KAFKA-1853: - Hi [~jkreps], I've updated the patch to take in

[jira] [Commented] (KAFKA-1853) Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283981#comment-14283981 ] jaikiran pai commented on KAFKA-1853: - Updated reviewboard https://reviews.apache.org/

[jira] [Updated] (KAFKA-1853) Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1853: Attachment: KAFKA-1853_2015-01-20_22:04:29.patch > Unsuccessful suffix rename of expired LogSegment

[jira] [Updated] (KAFKA-1885) Allow test methods in "core" to be individually run from outside of the IDE

[ https://issues.apache.org/jira/browse/KAFKA-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1885: Status: Patch Available (was: Open) > Allow test methods in "core" to be individually run from outs

[jira] [Commented] (KAFKA-1885) Allow test methods in "core" to be individually run from outside of the IDE

[ https://issues.apache.org/jira/browse/KAFKA-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283961#comment-14283961 ] jaikiran pai commented on KAFKA-1885: - Created reviewboard https://reviews.apache.org/

[jira] [Updated] (KAFKA-1885) Allow test methods in "core" to be individually run from outside of the IDE

[ https://issues.apache.org/jira/browse/KAFKA-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1885: Attachment: KAFKA-1885.patch > Allow test methods in "core" to be individually run from outside of t

[jira] [Updated] (KAFKA-1885) Allow test methods in "core" to be individually run from outside of the IDE

[ https://issues.apache.org/jira/browse/KAFKA-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1885: Description: Gradle in combination with Java plugin allows test "filtering" which lets users run se

[jira] [Updated] (KAFKA-1885) Allow test methods in "core" to be individually run from outside of the IDE

[ https://issues.apache.org/jira/browse/KAFKA-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1885: Description: Gradle in combination with Java plugin allows test "filtering" which lets users run se

[jira] [Created] (KAFKA-1885) Allow test methods in "core" to be individually run from outside of the IDE

jaikiran pai created KAFKA-1885: --- Summary: Allow test methods in "core" to be individually run from outside of the IDE Key: KAFKA-1885 URL: https://issues.apache.org/jira/browse/KAFKA-1885 Project: Kafk

[jira] [Updated] (KAFKA-1883) NullPointerException in RequestSendThread

[ https://issues.apache.org/jira/browse/KAFKA-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1883: Status: Patch Available (was: Open) > NullPointerException in RequestSendThread > -

[jira] [Updated] (KAFKA-1883) NullPointerException in RequestSendThread

[ https://issues.apache.org/jira/browse/KAFKA-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1883: Attachment: KAFKA-1883.patch > NullPointerException in RequestSendThread > -

[jira] [Commented] (KAFKA-1883) NullPointerException in RequestSendThread

[ https://issues.apache.org/jira/browse/KAFKA-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283366#comment-14283366 ] jaikiran pai commented on KAFKA-1883: - Created reviewboard https://reviews.apache.org/

[jira] [Created] (KAFKA-1883) NullPointerException in RequestSendThread

jaikiran pai created KAFKA-1883: --- Summary: NullPointerException in RequestSendThread Key: KAFKA-1883 URL: https://issues.apache.org/jira/browse/KAFKA-1883 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-1878) ProducerFailureHandlingTest.testCannotSendToInternalTopic fails with TimeoutException while trying to fetch metadata for topic

[ https://issues.apache.org/jira/browse/KAFKA-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282672#comment-14282672 ] jaikiran pai commented on KAFKA-1878: - Updated reviewboard https://reviews.apache.org/

[jira] [Updated] (KAFKA-1878) ProducerFailureHandlingTest.testCannotSendToInternalTopic fails with TimeoutException while trying to fetch metadata for topic

[ https://issues.apache.org/jira/browse/KAFKA-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1878: Attachment: KAFKA-1878_2015-01-19_22:02:54.patch > ProducerFailureHandlingTest.testCannotSendToInter

[jira] [Commented] (KAFKA-1878) ProducerFailureHandlingTest.testCannotSendToInternalTopic fails with TimeoutException while trying to fetch metadata for topic

[ https://issues.apache.org/jira/browse/KAFKA-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282338#comment-14282338 ] jaikiran pai commented on KAFKA-1878: - Created reviewboard https://reviews.apache.org/

[jira] [Updated] (KAFKA-1878) ProducerFailureHandlingTest.testCannotSendToInternalTopic fails with TimeoutException while trying to fetch metadata for topic

[ https://issues.apache.org/jira/browse/KAFKA-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1878: Attachment: KAFKA-1878.patch > ProducerFailureHandlingTest.testCannotSendToInternalTopic fails with

[jira] [Updated] (KAFKA-1878) ProducerFailureHandlingTest.testCannotSendToInternalTopic fails with TimeoutException while trying to fetch metadata for topic

[ https://issues.apache.org/jira/browse/KAFKA-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1878: Status: Patch Available (was: Open) > ProducerFailureHandlingTest.testCannotSendToInternalTopic fai

[jira] [Created] (KAFKA-1878) ProducerFailureHandlingTest.testCannotSendToInternalTopic fails with TimeoutException while trying to fetch metadata for topic

jaikiran pai created KAFKA-1878: --- Summary: ProducerFailureHandlingTest.testCannotSendToInternalTopic fails with TimeoutException while trying to fetch metadata for topic Key: KAFKA-1878 URL: https://issues.apache.or

[jira] [Commented] (KAFKA-1867) liveBroker list not updated on a cluster with no topics

[ https://issues.apache.org/jira/browse/KAFKA-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14281822#comment-14281822 ] jaikiran pai commented on KAFKA-1867: - Created reviewboard https://reviews.apache.org/

[jira] [Updated] (KAFKA-1867) liveBroker list not updated on a cluster with no topics

[ https://issues.apache.org/jira/browse/KAFKA-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1867: Attachment: KAFKA-1867.patch > liveBroker list not updated on a cluster with no topics > ---

[jira] [Comment Edited] (KAFKA-1837) Metadata record future never returns on get call after producer is stopped and messages can't be sent

[ https://issues.apache.org/jira/browse/KAFKA-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278351#comment-14278351 ] jaikiran pai edited comment on KAFKA-1837 at 1/15/15 6:54 AM: --

[jira] [Commented] (KAFKA-1837) Metadata record future never returns on get call after producer is stopped and messages can't be sent

[ https://issues.apache.org/jira/browse/KAFKA-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278351#comment-14278351 ] jaikiran pai commented on KAFKA-1837: - Paul, looking at the code, I can see why this i

[jira] [Comment Edited] (KAFKA-1854) Allow the JIRA username and password to be prompted during patch submission

[ https://issues.apache.org/jira/browse/KAFKA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278224#comment-14278224 ] jaikiran pai edited comment on KAFKA-1854 at 1/15/15 4:14 AM: --

[jira] [Issue Comment Deleted] (KAFKA-1854) Allow the JIRA username and password to be prompted during patch submission

[ https://issues.apache.org/jira/browse/KAFKA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1854: Comment: was deleted (was: Hi [~omkreddy] that page looks like a duplicate of this one https://cwik

[jira] [Comment Edited] (KAFKA-1854) Allow the JIRA username and password to be prompted during patch submission

[ https://issues.apache.org/jira/browse/KAFKA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278224#comment-14278224 ] jaikiran pai edited comment on KAFKA-1854 at 1/15/15 4:14 AM: --

[jira] [Commented] (KAFKA-1854) Allow the JIRA username and password to be prompted during patch submission

[ https://issues.apache.org/jira/browse/KAFKA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278224#comment-14278224 ] jaikiran pai commented on KAFKA-1854: - Hi [~omkreddy] that page looks like a duplicate

[jira] [Commented] (KAFKA-1854) Allow the JIRA username and password to be prompted during patch submission

[ https://issues.apache.org/jira/browse/KAFKA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278225#comment-14278225 ] jaikiran pai commented on KAFKA-1854: - Hi [~omkreddy] that page looks like a duplicate

[jira] [Commented] (KAFKA-1853) Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278129#comment-14278129 ] jaikiran pai commented on KAFKA-1853: - Hi Jay, Thank you explaining the reasoning beh

[jira] [Commented] (KAFKA-1854) Allow the JIRA username and password to be prompted during patch submission

[ https://issues.apache.org/jira/browse/KAFKA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14274787#comment-14274787 ] jaikiran pai commented on KAFKA-1854: - Thank you [~guozhang]! > Allow the JIRA usern

[jira] [Assigned] (KAFKA-1854) Allow the JIRA username and password to be prompted during patch submission

[ https://issues.apache.org/jira/browse/KAFKA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai reassigned KAFKA-1854: --- Assignee: jaikiran pai > Allow the JIRA username and password to be prompted during patch sub

[jira] [Updated] (KAFKA-1853) Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1853: Summary: Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the Log

[jira] [Commented] (KAFKA-1853) Unsuccessful suffix rename attempt of LogSegment can leak files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272498#comment-14272498 ] jaikiran pai commented on KAFKA-1853: - Created reviewboard https://reviews.apache.org/

[jira] [Commented] (KAFKA-1853) Unsuccessful suffix rename attempt of LogSegment can leak files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272492#comment-14272492 ] jaikiran pai commented on KAFKA-1853: - Hi [~jkreps], you are right about the Java File

[jira] [Commented] (KAFKA-1836) metadata.fetch.timeout.ms set to zero blocks forever

[ https://issues.apache.org/jira/browse/KAFKA-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272298#comment-14272298 ] jaikiran pai commented on KAFKA-1836: - Thanks [~nehanarkhede], I've updated the review

[jira] [Commented] (KAFKA-1854) Allow the JIRA username and password to be prompted during patch submission

[ https://issues.apache.org/jira/browse/KAFKA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270968#comment-14270968 ] jaikiran pai commented on KAFKA-1854: - Updated reviewboard https://reviews.apache.org/

[jira] [Updated] (KAFKA-1854) Allow the JIRA username and password to be prompted during patch submission

[ https://issues.apache.org/jira/browse/KAFKA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1854: Attachment: KAFKA-1854_2015-01-09_18:16:35.patch > Allow the JIRA username and password to be prompt

[jira] [Updated] (KAFKA-1854) Allow the JIRA username and password to be prompted during patch submission

[ https://issues.apache.org/jira/browse/KAFKA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1854: Attachment: KAFKA-1854_2015-01-09_15:42:28.patch > Allow the JIRA username and password to be prompt

[jira] [Commented] (KAFKA-1854) Allow the JIRA username and password to be prompted during patch submission

[ https://issues.apache.org/jira/browse/KAFKA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270839#comment-14270839 ] jaikiran pai commented on KAFKA-1854: - Updated reviewboard https://reviews.apache.org/

[jira] [Updated] (KAFKA-1854) Allow the JIRA username and password to be prompted during patch submission

[ https://issues.apache.org/jira/browse/KAFKA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1854: Status: Patch Available (was: Open) Patch has been submitted P.S: It looks like (while auto submit

[jira] [Updated] (KAFKA-1854) Allow the JIRA username and password to be prompted during patch submission

[ https://issues.apache.org/jira/browse/KAFKA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1854: Attachment: KAFKA-1854_2015-01-09_13:39:23.patch > Allow the JIRA username and password to be prompt

[jira] [Commented] (KAFKA-1854) Allow the JIRA username and password to be prompted during patch submission

[ https://issues.apache.org/jira/browse/KAFKA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270735#comment-14270735 ] jaikiran pai commented on KAFKA-1854: - Updated reviewboard https://reviews.apache.org/

[jira] [Updated] (KAFKA-1854) Allow the JIRA username and password to be prompted during patch submission

[ https://issues.apache.org/jira/browse/KAFKA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1854: Attachment: KAFKA-1854.patch > Allow the JIRA username and password to be prompted during patch subm

[jira] [Commented] (KAFKA-1854) Allow the JIRA username and password to be prompted during patch submission

[ https://issues.apache.org/jira/browse/KAFKA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270717#comment-14270717 ] jaikiran pai commented on KAFKA-1854: - Created reviewboard https://reviews.apache.org/

[jira] [Created] (KAFKA-1854) Allow the JIRA username and password to be prompted during patch submission

jaikiran pai created KAFKA-1854: --- Summary: Allow the JIRA username and password to be prompted during patch submission Key: KAFKA-1854 URL: https://issues.apache.org/jira/browse/KAFKA-1854 Project: Kafk

[jira] [Updated] (KAFKA-1853) Unsuccessful suffix rename attempt of LogSegment can leak files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1853: Summary: Unsuccessful suffix rename attempt of LogSegment can leak files and also leave the LogSegme

[jira] [Updated] (KAFKA-1853) Unsuccesful suffix rename attempt of LogSegment can leak files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1853: Status: Patch Available (was: Open) Created reviewboard https://reviews.apache.org/r/29755/diff aga

[jira] [Commented] (KAFKA-1853) Unsuccesful suffix rename attempt of LogSegment can leak files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270627#comment-14270627 ] jaikiran pai commented on KAFKA-1853: - I've a patch for this which I'll submit in a wh

[jira] [Created] (KAFKA-1853) Unsuccesful suffix rename attempt of LogSegment can leak files and also leave the LogSegment in an invalid state

jaikiran pai created KAFKA-1853: --- Summary: Unsuccesful suffix rename attempt of LogSegment can leak files and also leave the LogSegment in an invalid state Key: KAFKA-1853 URL: https://issues.apache.org/jira/browse/

[jira] [Commented] (KAFKA-1836) metadata.fetch.timeout.ms set to zero blocks forever

[ https://issues.apache.org/jira/browse/KAFKA-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270525#comment-14270525 ] jaikiran pai commented on KAFKA-1836: - Thanks Ewen for your feedback. I've taken into

[jira] [Updated] (KAFKA-1836) metadata.fetch.timeout.ms set to zero blocks forever

[ https://issues.apache.org/jira/browse/KAFKA-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1836: Attachment: KAFKA-1836-new-patch.patch > metadata.fetch.timeout.ms set to zero blocks forever >

[jira] [Comment Edited] (KAFKA-1661) Move MockConsumer and MockProducer from src/main to src/test

[ https://issues.apache.org/jira/browse/KAFKA-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265649#comment-14265649 ] jaikiran pai edited comment on KAFKA-1661 at 1/6/15 3:45 AM: -

[jira] [Commented] (KAFKA-1661) Move MockConsumer and MockProducer from src/main to src/test

[ https://issues.apache.org/jira/browse/KAFKA-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265649#comment-14265649 ] jaikiran pai commented on KAFKA-1661: - I think it's a matter of how Kafka wants to cla

[jira] [Commented] (KAFKA-1661) Move MockConsumer and MockProducer from src/main to src/test

[ https://issues.apache.org/jira/browse/KAFKA-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264286#comment-14264286 ] jaikiran pai commented on KAFKA-1661: - Perhaps having those mock implementations in "e