You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Greg Solovyev (Jira)" <ji...@apache.org> on 2019/10/03 02:36:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16943292#comment-16943292 ]
Greg Solovyev commented on KUDU-2536:
-------------------------------------
Having read the [review|[https://gerrit.cloudera.org/c/4793/]] for 3a3f714e4 I am not sure if there was a specific reason for not checking log_block_manager_test_hole_punching flag in the new code. [~adar] do you recall why you removed the reference to this flag?
> 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
(v8.3.4#803005)