[ 
https://issues.apache.org/jira/browse/HDFS-16943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17708115#comment-17708115
 ] 

ASF GitHub Bot commented on HDFS-16943:
---------------------------------------

simbadzina commented on code in PR #5469:
URL: https://github.com/apache/hadoop/pull/5469#discussion_r1156449098


##########
hadoop-hdfs-project/hadoop-hdfs-rbf/src/main/java/org/apache/hadoop/hdfs/server/federation/store/driver/impl/StateStoreBaseImpl.java:
##########
@@ -39,6 +40,7 @@
  * optimization, such as custom get/put/remove queries, depending on the
  * capabilities of the data store.
  */
[email protected]
 public abstract class StateStoreBaseImpl extends StateStoreDriver {

Review Comment:
   Fixed.





> 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]

Reply via email to