You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2017/08/22 05:10:00 UTC

[jira] [Resolved] (KUDU-1685) File Block Manager's block ID's are stored inefficiently

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

Todd Lipcon resolved KUDU-1685.
-------------------------------
       Resolution: Won't Fix
    Fix Version/s: n/a

Unfortunately I don't think we can change this now, since re-arranging the layout of an existing block manager would break compatibility. We've decided that the FBM is for small dev setups only, though, so I'm not too sad about it.

> File Block Manager's block ID's are stored inefficiently
> --------------------------------------------------------
>
>                 Key: KUDU-1685
>                 URL: https://issues.apache.org/jira/browse/KUDU-1685
>             Project: Kudu
>          Issue Type: Bug
>          Components: tserver
>    Affects Versions: 1.0.0
>            Reporter: Attila Bukor
>             Fix For: n/a
>
>
> The fix for KUDU-1538 causes too many block IDs to be stored in the same directory:
> {code}
> $ tree -d
> .
> └── d1
>     └── 1e
>         └── fe
> {code}
> Storing it in LSB order should probably be better.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)