[
https://issues.apache.org/jira/browse/HDFS-16943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17698565#comment-17698565
]
ASF GitHub Bot commented on HDFS-16943:
---------------------------------------
virajjasani commented on PR #5469:
URL: https://github.com/apache/hadoop/pull/5469#issuecomment-1462592962
I don't have much insights into Yarn federation but it looks like Yarn does
have `SQLFederationStateStore` (it uses `HikariDataSource`) and one of the impl
`MySQLFederationStateStore` is in test code.
Perhaps keeping MySQL specific impl in test was meant to be set as an
example only? @slfan1989 might have better insights.
I don't mean anything against this change btw, I just wonder how we could
manage ever increasing num of external dependencies such that we could allow
more pluggable implementation to be used by different users without hadoop
having to take up more external dependencies :)
> RBF: Implement MySQL based StateStoreDriver
> -------------------------------------------
>
> Key: HDFS-16943
> URL: https://issues.apache.org/jira/browse/HDFS-16943
> Project: Hadoop HDFS
> Issue Type: Task
> Components: hdfs, rbf
> Reporter: Simbarashe Dzinamarira
> Assignee: Simbarashe Dzinamarira
> Priority: Major
> Labels: pull-request-available
>
> RBF supports two types of StateStoreDrivers
> # StateStoreFileImpl
> # StateStoreZooKeeperImpl
> I propose implementing a third driver that is backed by MySQL.
> * StateStoreZooKeeperImpl requires an additional Zookeeper cluster.
> * StateStoreFileImpl can use one of the namenodes in the HDFS cluster, but
> that namenode becomes a single point of failure, introducing coupling between
> the federated clusters.
> HADOOP-18535 implemented a MySQL token store. When tokens are stored in
> MySQL, using MySQL for the StateStore as well reduces the number of external
> dependencies for routers.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
