You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "YifanZhang (Jira)" <ji...@apache.org> on 2020/05/14 04:19:00 UTC

[jira] [Commented] (KUDU-3121) Allow users to pick the next best op

    [ https://issues.apache.org/jira/browse/KUDU-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17106875#comment-17106875 ] 

YifanZhang commented on KUDU-3121:
----------------------------------

Maybe this issue is similar to KUDU-2824, now we can use 'kudu table set_flag' tool to give some tables a high priority in MM compaction.

And also according to [~wdberkeley_impala_f7d4]'s suggestion inĀ [https://gerrit.cloudera.org/c/12852/], we could also improveĀ the maintenance manager by accounting for how often tablets are read or written.

> Allow users to pick the next best op
> ------------------------------------
>
>                 Key: KUDU-3121
>                 URL: https://issues.apache.org/jira/browse/KUDU-3121
>             Project: Kudu
>          Issue Type: New Feature
>          Components: ops-tooling
>            Reporter: Andrew Wong
>            Priority: Major
>
> Time and again, we'll see a case where the maintenance manager scheduler thread is, for whatever reason, scheduling an op that is actually not that helpful. KUDU-2929, KUDU-3002, and KUDU-1400 come to mind.
> It might be convenient in some cases to temporarily (maybe for a single round of scheduling) give a specific tablet or op priority.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)