You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Grant Henke (Jira)" <ji...@apache.org> on 2020/06/03 15:59:00 UTC

[jira] [Updated] (KUDU-3024) kudu-master: scale test for high number of simultanenous updates on tables metadata

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

Grant Henke updated KUDU-3024:
------------------------------
    Labels: benchmarks  (was: )

> kudu-master: scale test for high number of simultanenous updates on tables metadata
> -----------------------------------------------------------------------------------
>
>                 Key: KUDU-3024
>                 URL: https://issues.apache.org/jira/browse/KUDU-3024
>             Project: Kudu
>          Issue Type: Test
>          Components: perf, test
>            Reporter: Alexey Serbin
>            Priority: Major
>              Labels: benchmarks
>
> It would be nice to have a scale test to verify how Kudu masters behave when there is a high number of almost simultaneous updates in tables' metadata (e.g., ALTER table to add a new partition, add new columns, drop columns, etc.).  At least, it would be able to spot issues like KUDU-3016.



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