Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-3652

Parameterize resource request of PVC for storage

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Unresolved
    • Major
    • None
    • 2.7 ER1
    • 3scale Operator
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • 0
    • 0% 0%

    Description

      Default 3scale storage space is 1GB when deployed by the Operator. This can be insufficient for some customers in the future.

      We faced this problem when MySQL depleted all available space in a 3scale instance deployed by Delorean (it has storage claim 1GB as well). As a result of that, deployment system-mysql pod fails with the error message: 

      [Warning] InnoDB: 1048576 bytes should have been written. Only 1015808 bytes written. Retrying for the remaining bytes.
[Warning] InnoDB: Retry attempts for writing partial data failed.
ERROR] InnoDB: Write to file ./ibtmp1failed at offset 11534336, 1048576 bytes should have been written, only 1015808 were written. Operating system error number 28. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded.
[ERROR] InnoDB: Error number 28 means 'No space left on device'

      Dev Notes:
      This issue applies to all PVCs exposed by the APIManager CRD. Currently only storageclass is configurable. This issue is to add resource request as well

      Attachments

        Issue Links

          is duplicated by

          Feature Request - Feature requests from customers and/or users THREESCALE-9002 Make resource request configurable for backend and system redis PVCs

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Sub-task - The sub-task of the issue THREESCALE-5051 Custom storage class per PVC - implementation

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) THREESCALE-9330 There is no official documentation to resize PVs

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Defined

          Activity

            People

              Unassigned Unassigned
              jsmolar Jakub Smolár
              Matej Dujava Matej Dujava
              Eguzki Astiz Lezaun Eguzki Astiz Lezaun
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated: