You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Bessonov (Jira)" <ji...@apache.org> on 2020/04/13 13:41:00 UTC

[jira] [Resolved] (IGNITE-12721) Validation of key length written to Distributed Metastorage

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

Ivan Bessonov resolved IGNITE-12721.
------------------------------------
    Release Note: Issue is irrelevant because IGNITE-12726 is already fixed.
      Resolution: Won't Fix

> Validation of key length written to Distributed Metastorage
> -----------------------------------------------------------
>
>                 Key: IGNITE-12721
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12721
>             Project: Ignite
>          Issue Type: Task
>          Components: persistence
>            Reporter: Sergey Chugunov
>            Assignee: Sergey Chugunov
>            Priority: Major
>             Fix For: 2.9
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> DistributedMetastorage functionality introduced in IGNITE-10640 provides convenient way to perform coordinated writes to local MetaStorages on all server nodes but lacks important part: validation of key length.
> Current implementation of MetaStorage doesn't allow keys longer than a specific value (64 bytes minus some prefixes, see source code for details) and throws assertion error on an attempt to write longer key.
> This error from MetaStorage is not propagated to DistributedMetastorage and (in theory) may even cause a node to halt.
> In order to avoid this situation validation of key length should be added right to DistributedMetastorage implementation to enforce "fail-fast" principle and preserve Ignite nodes from potentially dangerous consequences.



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