[jira] [Created] (KAFKA-8308) Update jetty for security vulnerability CVE-2019-10241

2019-04-30 Thread Di Shang (JIRA)
Di Shang created KAFKA-8308: --- Summary: Update jetty for security vulnerability CVE-2019-10241 Key: KAFKA-8308 URL: https://issues.apache.org/jira/browse/KAFKA-8308 Project: Kafka Issue Type: Task

[jira] [Commented] (KAFKA-4453) add request prioritization

2019-04-10 Thread Di Shang (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814078#comment-16814078 ] Di Shang commented on KAFKA-4453: - Hi The new metric introduced here breaks our metric parser with NaN

[jira] [Commented] (KAFKA-6769) Upgrade jetty library version

2018-04-10 Thread Di Shang (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16433282#comment-16433282 ] Di Shang commented on KAFKA-6769: - So it looks like https://issues.apache.org/jira/browse/KAFKA-4423 (drop

[jira] [Created] (KAFKA-6769) Upgrade jetty library version

2018-04-09 Thread Di Shang (JIRA)
Di Shang created KAFKA-6769: --- Summary: Upgrade jetty library version Key: KAFKA-6769 URL: https://issues.apache.org/jira/browse/KAFKA-6769 Project: Kafka Issue Type: Task Components:

[jira] [Commented] (KAFKA-6706) NETWORK_EXCEPTION and REQUEST_TIMED_OUT in mirrormaker producer after 1.0 broker upgrade

2018-04-05 Thread Di Shang (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427950#comment-16427950 ] Di Shang commented on KAFKA-6706: - Upgrading broker to Kafka 1.1.0 seems to resolve the issue (haven't

[jira] [Updated] (KAFKA-6706) NETWORK_EXCEPTION and REQUEST_TIMED_OUT in mirrormaker producer after 1.0 broker upgrade

2018-03-28 Thread Di Shang (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Shang updated KAFKA-6706: Description: We have 2 clusters A and B with 4 brokers each, we use mirrormaker to replicate topics from A

[jira] [Updated] (KAFKA-6706) NETWORK_EXCEPTION and REQUEST_TIMED_OUT in mirrormaker producer after 1.0 broker upgrade

2018-03-28 Thread Di Shang (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Shang updated KAFKA-6706: Description: We have 2 clusters A and B with 4 brokers each, we use mirrormaker to replicate topics from A

[jira] [Updated] (KAFKA-6706) NETWORK_EXCEPTION and REQUEST_TIMED_OUT in mirrormaker producer after 1.0 broker upgrade

2018-03-28 Thread Di Shang (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Shang updated KAFKA-6706: Priority: Blocker (was: Major) Description: We have 2 clusters A and B with 4 brokers each, we use

[jira] [Commented] (KAFKA-6706) NETWORK_EXCEPTION and REQUEST_TIMED_OUT in mirrormaker producer after 1.0 broker upgrade

2018-03-25 Thread Di Shang (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16413355#comment-16413355 ] Di Shang commented on KAFKA-6706: - @[~sunzhenya] I have read through KIP-91 before but it's not even

[jira] [Created] (KAFKA-6706) NETWORK_EXCEPTION and REQUEST_TIMED_OUT in mirrormaker producer after 1.0 broker upgrade

2018-03-23 Thread Di Shang (JIRA)
Di Shang created KAFKA-6706: --- Summary: NETWORK_EXCEPTION and REQUEST_TIMED_OUT in mirrormaker producer after 1.0 broker upgrade Key: KAFKA-6706 URL: https://issues.apache.org/jira/browse/KAFKA-6706