Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/16521#discussion_r95661186
--- Diff: docs/configuration.md ---
@@ -1625,40 +1625,40 @@ Apart from these, the following properties are also
available, and may be useful
</td>
</tr>
<tr>
- <td><code>spark.authenticate.enableSaslEncryption</code></td>
+ <td><code>spark.network.crypto.enabled</code></td>
<td>false</td>
<td>
- Enable encrypted communication when authentication is
- enabled. This is supported by the block transfer service and the
- RPC endpoints.
+ Enable encryption using the commons-crypto library for RPC and block
transfer service.
+ Requires <code>spark.authenticate</code> to be enabled.
--- End diff --
if `spark.authenticate=false`, what happens if this is `true`? It looks
like it is just ignored, I think fail-fast would be ideal.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
