[
https://issues.apache.org/jira/browse/YARN-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451589#comment-15451589
]
Lavkesh Lahngir commented on YARN-5123:
---------------------------------------
[~giovanni.fumarola] : It's an arbitrary choice. Because we can Implement HSQL
as easy as any other database. We just have to make sure that the fencing
assumptions works. For this, we can refactor the code and put an abstract class
which can provide few common use cases. Other implementation should override
the syntax which is specific to the DB implementation (i.e. Postgres or HSQL)
> SQL based RM state store
> ------------------------
>
> Key: YARN-5123
> URL: https://issues.apache.org/jira/browse/YARN-5123
> Project: Hadoop YARN
> Issue Type: New Feature
> Reporter: Lavkesh Lahngir
> Assignee: Lavkesh Lahngir
> Attachments: 0001-SQL-Based-RM-state-store-trunk.patch, High
> Availability In YARN Resource Manager using SQL Based StateStore.pdf,
> sqlstatestore.patch
>
>
> In our setup, zookeeper based RM state store didn't work. We ended up
> implementing our own SQL based state store. Here is a patch, if anybody else
> wants to use it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
