You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2019/09/11 12:31:09 UTC

[GitHub] [pulsar] cdbartholomew commented on issue #5151: Broker fails to start with function worker enabled and broker client using TLS

cdbartholomew commented on issue #5151: Broker fails to start with function worker enabled and broker client using TLS
URL: https://github.com/apache/pulsar/pull/5151#issuecomment-530358745
 
 
   @jiazhai , thanks for the feedback. I agree with your comment about`workerConfig.isUseTls. Now that I think about it more, with the change I have proposed there is no way to use TLS for connecting to other brokers (especially geo-replicated ones) but to not use TLS for the function worker running locally with the broker. When running locally there is no need to encrypt the traffic, so the overhead may not be wanted. 
   
   If I revert the change on line 163, then the user can choose whether to run the local function worker with TLS or not using the worker config. I will make that change and test it out.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services