[
https://issues.apache.org/jira/browse/BEAM-6182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733648#comment-16733648
]
Ahmet Altay commented on BEAM-6182:
-----------------------------------
The state of things, as far as I know is:
* Conscrypt is disabled by default. (As a side note, this results in 15%
performance regressions however enabling conscrypt by default is blocked on
underlying issues in conscrypt.)
* The above in combination with vendoring resulted in issues. GRPC required
either conscrypt (disabled by default) or netty (broken by vendoring). Scott
fixed the vendoring issue. This should not be a problem any more. We need to
validate in during release validation using the test Cham added
([https://github.com/apache/beam/pull/7365)]
I believe doing the validation is the only remaining item for 2.10. We can keep
the issue for long-term to re-enable conscrypt once there is a new bug-fixed
conscrypt version.
> Use of conscrypt SSL results in stuck workflows in Dataflow
> -----------------------------------------------------------
>
> Key: BEAM-6182
> URL: https://issues.apache.org/jira/browse/BEAM-6182
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Reporter: Ahmet Altay
> Assignee: Tyler Akidau
> Priority: Blocker
> Fix For: 2.10.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> An experimental flag is being added to disable it for now with an option to
> enable it per-workflow.
> Also related:
> https://issues.apache.org/jira/browse/BEAM-5747 - Upgrade conscrypt to its
> latest version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
