[
https://issues.apache.org/jira/browse/HADOOP-18535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17680315#comment-17680315
]
ASF GitHub Bot commented on HADOOP-18535:
-----------------------------------------
hchaverri opened a new pull request, #5325:
URL: https://github.com/apache/hadoop/pull/5325
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
These changes follow the same logic used in the existing ZK based secret
manager implementation.
1. Minor changes to DelegationTokenInformation class so it's easier to
convert to byte array format.
2. SQLDelegationTokenSecretManager transforms tokens and delegation keys
into expected format and delegates the storage operations to the implementation
class.
3. SQLDelegationTokenSecretManagerImpl interacts with SQL storage.
4. DistributedSQLCounter is used to manage sequenceNumbers and
delegationKeyIds in a distributed way.
5. Including SQL schema files to create sample database, tables and users.
### How was this patch tested?
Executed operations for token creation, renewal and cancellation. Compared
results with existing ZK implementation.
### For code changes:
- [Y] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [Y] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [Y] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [NA] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> Implement token storage solution based on MySQL
> -----------------------------------------------
>
> Key: HADOOP-18535
> URL: https://issues.apache.org/jira/browse/HADOOP-18535
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Hector Sandoval Chaverri
> Assignee: Hector Sandoval Chaverri
> Priority: Major
> Labels: pull-request-available
>
> Hadoop RBF supports custom implementations of secret managers. At the moment,
> the only available implementation is ZKDelegationTokenSecretManagerImpl,
> which stores tokens and delegation keys in Zookeeper.
> During our investigation, we found that the performance of routers is limited
> by the writes to the Zookeeper token store, which impacts requests for token
> creation, renewal and cancellation. An alternative secret manager
> implementation has been created, based on MySQL, to handle a higher number of
> writes.
> We measured the throughput of each token operation (create/renew/cancel) on
> different setups and obtained the following results:
> # Sending requests directly to Namenode (no RBF):
> Token creations: 290 reqs per sec
> Token renewals: 86 reqs per sec
> Token cancellations: 97 reqs per sec
> # Sending requests to routers using Zookeeper based secret manager:
> Token creations: 31 reqs per sec
> Token renewals: 29 reqs per sec
> Token cancellations: 40 reqs per sec
> # Sending requests to routers using SQL based secret manager:
> Token creations: 241 reqs per sec
> Token renewals: 103 reqs per sec
> Token cancellations: 114 reqs per sec
> We noticed a significant improvement when using a SQL secret manager,
> comparable to the throughput offered by Namenodes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
