[jira] [Updated] (KAFKA-3053) wrong output in log at Log#recoverLog()

2015-12-30 Thread Xing Huang (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xing Huang updated KAFKA-3053: -- Description: In Log#recoverLog() // we had an invalid message, delete all remaining log

[jira] [Created] (KAFKA-3053) wrong output in log at Log#recoverLog()

2015-12-30 Thread Xing Huang (JIRA)
Xing Huang created KAFKA-3053: - Summary: wrong output in log at Log#recoverLog() Key: KAFKA-3053 URL: https://issues.apache.org/jira/browse/KAFKA-3053 Project: Kafka Issue Type: Bug Com

Build failed in Jenkins: kafka-trunk-jdk7 #930

2015-12-30 Thread Apache Jenkins Server
See Changes: [cshapi] MINOR: fixing typos in docs -- [...truncated 4746 lines...] org.apache.kafka.connect.storage.OffsetStorageWriterTest > testNoOffsetsToFlush PASSED org.apache.kafka.connect

[jira] [Commented] (KAFKA-3052) broker properties get logged twice if acl is enabled

2015-12-30 Thread Gwen Shapira (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075609#comment-15075609 ] Gwen Shapira commented on KAFKA-3052: - >From what I can see, the simplest fix would be

[GitHub] kafka pull request: MINOR: fixing typos in docs

2015-12-30 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/721 --- 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 enabl

[jira] [Updated] (KAFKA-3052) broker properties get logged twice if acl is enabled

2015-12-30 Thread Dong Lin (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-3052: Assignee: (was: Dong Lin) > broker properties get logged twice if acl is enabled > -

[jira] [Assigned] (KAFKA-3052) broker properties get logged twice if acl is enabled

2015-12-30 Thread Dong Lin (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin reassigned KAFKA-3052: --- Assignee: Dong Lin > broker properties get logged twice if acl is enabled > -

[jira] [Created] (KAFKA-3052) broker properties get logged twice if acl is enabled

2015-12-30 Thread Jun Rao (JIRA)
Jun Rao created KAFKA-3052: -- Summary: broker properties get logged twice if acl is enabled Key: KAFKA-3052 URL: https://issues.apache.org/jira/browse/KAFKA-3052 Project: Kafka Issue Type: Improvemen

[jira] [Updated] (KAFKA-3048) incorrect property name ssl.want.client.auth

2015-12-30 Thread Jun Rao (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3048: --- Fix Version/s: 0.9.0.1 > incorrect property name ssl.want.client.auth > -

[jira] [Updated] (KAFKA-3045) ZkNodeChangeNotificationListener shouldn't log interrupted exception as error

2015-12-30 Thread Jun Rao (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3045: --- Fix Version/s: 0.9.0.1 > ZkNodeChangeNotificationListener shouldn't log interrupted exception as error > -

[jira] [Created] (KAFKA-3051) security.protocol documentation is inaccurate

2015-12-30 Thread Jun Rao (JIRA)
Jun Rao created KAFKA-3051: -- Summary: security.protocol documentation is inaccurate Key: KAFKA-3051 URL: https://issues.apache.org/jira/browse/KAFKA-3051 Project: Kafka Issue Type: Improvement

[GitHub] kafka pull request: MINOR: fixing typos in docs

2015-12-30 Thread samjhecht
GitHub user samjhecht opened a pull request: https://github.com/apache/kafka/pull/721 MINOR: fixing typos in docs This commit contains minor grammatical fixes. Some of the changes are just removing rogue commas, which can be hard to see in the diff. This contribution is

[jira] [Updated] (KAFKA-3050) Space in the value for "host.name" causes "Unresolved address"

2015-12-30 Thread Navin Markandeya (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Navin Markandeya updated KAFKA-3050: Description: In {{/config/server.properties}}, after updating the {{host.name}} to a valu

[jira] [Created] (KAFKA-3050) Space in the value for "host.name" causes "Unresolved address"

2015-12-30 Thread Navin Markandeya (JIRA)
Navin Markandeya created KAFKA-3050: --- Summary: Space in the value for "host.name" causes "Unresolved address" Key: KAFKA-3050 URL: https://issues.apache.org/jira/browse/KAFKA-3050 Project: Kafka

Build failed in Jenkins: kafka-trunk-jdk7 #929

2015-12-30 Thread Apache Jenkins Server
See Changes: [cshapi] Minor: fix sasl.kerberos.service.name -- [...truncated 4742 lines...] org.apache.kafka.connect.runtime.standalone.StandaloneHerderTest > testCreateSinkConnector PASSED org

[GitHub] kafka pull request: fix sasl.kerberos.service.name

2015-12-30 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/720 --- 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 enabl

[jira] [Commented] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

2015-12-30 Thread Petri Lehtinen (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15074867#comment-15074867 ] Petri Lehtinen commented on KAFKA-3042: --- I've seen the same thing happen on version

[GitHub] kafka pull request: fix sasl.kerberos.service.name

2015-12-30 Thread secjex
GitHub user secjex opened a pull request: https://github.com/apache/kafka/pull/720 fix sasl.kerberos.service.name sasl.kerberos.service.name surround by double quote didn't work, have to remove. You can merge this pull request into a Git repository by running: $ git pull https