You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Adar Dembo (JIRA)" <ji...@apache.org> on 2016/04/07 23:50:25 UTC

[jira] [Updated] (KUDU-423) Implement scalable and performant on-disk storage

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

Adar Dembo updated KUDU-423:
----------------------------
    Priority: Major  (was: Blocker)

bq. Perhaps we should downgrade the priority of this JIRA? Blocker doesn't seem appropriate since this is more a longer-term umbrella for improvements to this already-shipping feature.

Sure.

> Implement scalable and performant on-disk storage
> -------------------------------------------------
>
>                 Key: KUDU-423
>                 URL: https://issues.apache.org/jira/browse/KUDU-423
>             Project: Kudu
>          Issue Type: New Feature
>          Components: fs
>    Affects Versions: M4
>            Reporter: Todd Lipcon
>            Assignee: Adar Dembo
>              Labels: kudu-roadmap, scalability
>
> Our current on-disk storage has a number of issues:
> - only writes to one local disk (need to scale to at least 12)
> - exhausts file descriptors quickly (see KUDU-56)
> - causes a ton of seeks at startup (KUDU-374)
> - has big latency stalls on write due to ext4 journal-related chunky writeback
> - doesn't support features we'll eventually want to support such as tiered storage



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