You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Mike Percy (JIRA)" <ji...@apache.org> on 2016/02/26 12:49:18 UTC

[jira] [Updated] (KUDU-500) Changes to SysTables should be queryable on follower leaders upon replication

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

Mike Percy updated KUDU-500:
----------------------------
    Parent: KUDU-422

> Changes to SysTables should be queryable on follower leaders upon replication
> -----------------------------------------------------------------------------
>
>                 Key: KUDU-500
>                 URL: https://issues.apache.org/jira/browse/KUDU-500
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: master
>    Affects Versions: M5
>            Reporter: Alex Feinberg
>            Assignee: Alex Feinberg
>
> Currently CatalogManager serves requests from its in-memory objects. However, these objects are not updated on the replicas. There are two approaches for this: one is to serve CatalogManager from the underlying tablet (accepting potential latency hits, but making the implementation simpler), another is to implement callbacks on transaction completion on replicas (like MarkDirty but called whenever writes are committed on a replica).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)