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 2018/08/10 00:00:39 UTC

[jira] [Updated] (KUDU-2536) Make log_block_manager_test_hole_punching work again

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

Adar Dembo updated KUDU-2536:
-----------------------------
    Component/s: fs

> Make log_block_manager_test_hole_punching work again
> ----------------------------------------------------
>
>                 Key: KUDU-2536
>                 URL: https://issues.apache.org/jira/browse/KUDU-2536
>             Project: Kudu
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 1.8.0
>            Reporter: Adar Dembo
>            Priority: Major
>              Labels: newbie
>
> Commit 3a3f714e4 removed the last reference to this gflag but left it around. We should get it working again; there are times when it can be useful to skip the hole punch test and allow an LBM to be started on a filesystem even if it doesn't support hole punching.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)