[GitHub] kafka pull request #2564: KAFKA-4777 fix client heartbeat non-stop retry iss...

2017-02-17 Thread allenxiang
GitHub user allenxiang opened a pull request:

https://github.com/apache/kafka/pull/2564

KAFKA-4777 fix client heartbeat non-stop retry issue.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/allenxiang/kafka client-heartbeat-fix

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2564.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2564


commit 7500062262e9dceddfa9bc6413fe815b50c73c11
Author: Allen Xiang <allen.xi...@monsanto.com>
Date:   2017-02-17T20:04:02Z

KAFKA-4777 fix client heartbeat non-stop retry issue.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2446: KAFKA-4701: Add dynamic truststore manager.

2017-01-26 Thread allenxiang
GitHub user allenxiang opened a pull request:

https://github.com/apache/kafka/pull/2446

KAFKA-4701: Add dynamic truststore manager.

Allow kafka brokers to dynamically reload truststore without restarting.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/allenxiang/kafka trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2446.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2446


commit 4efbebd6fc769c5e2885f2fc8f029ff53b797b62
Author: Allen Xiang <allen.xi...@monsanto.com>
Date:   2017-01-26T14:48:02Z

KAFKA-4701: Allow kafka brokers to dynamically reload truststore without 
restarting.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2028: Replace default X509TrustManager with ReloadableX5...

2016-10-14 Thread allenxiang
Github user allenxiang closed the pull request at:

https://github.com/apache/kafka/pull/2028


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2028: Replace default X509TrustManager with ReloadableX5...

2016-10-14 Thread allenxiang
GitHub user allenxiang opened a pull request:

https://github.com/apache/kafka/pull/2028

Replace default X509TrustManager with ReloadableX509TrustManager.

ReloadableX509TrustManager will allow us to replace broker tuststore at any 
time without restart the broker.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/allenxiang/kafka trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2028.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2028


commit 7514359bd3d6f4a13d373f70abd3a92150714a89
Author: Allen Xiang <allen.xi...@monsanto.com>
Date:   2016-10-14T13:13:26Z

Replace default X509TrustManager with ReloadableX509TrustManager.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---