You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Arina Ielchiieva (Jira)" <ji...@apache.org> on 2019/11/04 12:54:00 UTC

[jira] [Updated] (DRILL-7191) RM blobs persistence in Zookeeper for Distributed RM

     [ https://issues.apache.org/jira/browse/DRILL-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arina Ielchiieva updated DRILL-7191:
------------------------------------
    Fix Version/s:     (was: 1.17.0)

> RM blobs persistence in Zookeeper for Distributed RM
> ----------------------------------------------------
>
>                 Key: DRILL-7191
>                 URL: https://issues.apache.org/jira/browse/DRILL-7191
>             Project: Apache Drill
>          Issue Type: Sub-task
>          Components:  Server, Query Planning &amp; Optimization
>    Affects Versions: 1.17.0
>            Reporter: Hanumath Rao Maduri
>            Assignee: Sorabh Hamirwasia
>            Priority: Major
>
> Changes to support storing UUID for each Drillbit Service Instance locally to be used by planner and execution layer. This UUID is used to uniquely identify a Drillbit and register Drillbit information in the RM StateBlobs.
> Introduced a PersistentStore named ZookeeperTransactionalPersistenceStore with Transactional capabilities using Zookeeper Transactional API’s. This is used for updating RM State blobs as all the updates need to happen in transactional manner. Added RMStateBlobs definition and support for serde to Zookeeper.
> Implementation for DistributedRM and its corresponding QueryRM apis and state management.
> Updated the state management of Query in Foreman so that same Foreman object can be submitted multiple times. Also introduced concept of 2 maps keeping track of waiting and running queries. These were done to support for async admit protocol which will be needed with Distributed RM.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)