Skip to content

Add compile-time configuration for maximum Key-Value Storage (KVS) size #161

@atarekra

Description

@atarekra

Description

The current Key-Value Storage (KVS) implementation does not provide a mechanism to define or restrict the maximum total storage size at compile time.
This capability is necessary to ensure that persistent storage usage remains predictable and compliant with the memory constraints.

Requirement Reference

“The Key-Value-Storage shall support specification of its maximum size at compile time.”
https://eclipse-score.github.io/score/main/features/persistency/kvs/requirements/index.html

Current Behavior

-The maximum storage size is not enforced or configurable at compile time.
-There is no compile-time verification or enforcement of maximum storage size, which can lead to unpredictable memory use.

Expected Behavior

-The maximum KVS size should be defined and validated at compile time.
-KVS shall prevent further writes once the compile-time limit is reached, returning an appropriate error code

Implementation Summary

A compile-time configuration option has been implemented (in cpp) to fulfill the requirement and we would like to share it with you for review.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions