Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-4141

AMQ Broker Operator: increasing PV size requires manual involvement even after recreating statefulset

    XMLWordPrintable

Details

    • Bug
    • Status: New
    • Major
    • Resolution: Unresolved
    • AMQ 7.7.0.CON.2.GA
    • None
    • operator
    • None
    • Hide

      1) Create a Broker CR which declares that requested storage size is 1GiB:

      storage:
        size: 1G
      

      2) Pod creates here just fine, allocates 1GB of storage

       

      3) Delete original CR

       

      4) Create a new CR with same name which would request 5GB of storage

       

      5) Here, previous PVC with size=1GB is reused. New PVC is not created. Storage stays 1GB.

      Show
      1) Create a Broker CR which declares that requested storage size is 1GiB: storage: size: 1G 2) Pod creates here just fine, allocates 1GB of storage   3) Delete original CR   4) Create a new CR with same name which would request 5GB of storage   5) Here, previous PVC with size=1GB is reused. New PVC is not created. Storage stays 1GB.
    • Workaround Exists
    • Hide

      simply removing PVC by-hand remedies the situation.

      Show
      simply removing PVC by-hand remedies the situation.
    • Hide
      If you try to increase the size of the Persistent Volume Claim (PVC) required by brokers in a deployment for persistent storage, the change does not take effect without further manual steps. For example, suppose that you configure the `storage.size` property of a Custom Resource (CR) instance to specify an initial size for the PVC. If you modify the CR to specify a __different__ value of `storage.size`, the existing brokers continue to use the original PVC size. This is the case even if you scale the deployment down to zero brokers and then back up to the original number. However, if you scale the size of the deployment up to add additional brokers, the new brokers use the new PVC size.

      To work around this issue, and ensure that all brokers in the deployment use the same PVC size, use the OpenShift Container Platform web console to expand the PVC size used by the deployment. In the console, click *Storage > Persistent Volume Claims*. Click your deployment. On the *Actions* drop-down menu in the top-right corner, select `Expand PVC` and enter a new value.
      Show
      If you try to increase the size of the Persistent Volume Claim (PVC) required by brokers in a deployment for persistent storage, the change does not take effect without further manual steps. For example, suppose that you configure the `storage.size` property of a Custom Resource (CR) instance to specify an initial size for the PVC. If you modify the CR to specify a __different__ value of `storage.size`, the existing brokers continue to use the original PVC size. This is the case even if you scale the deployment down to zero brokers and then back up to the original number. However, if you scale the size of the deployment up to add additional brokers, the new brokers use the new PVC size. To work around this issue, and ensure that all brokers in the deployment use the same PVC size, use the OpenShift Container Platform web console to expand the PVC size used by the deployment. In the console, click *Storage > Persistent Volume Claims*. Click your deployment. On the *Actions* drop-down menu in the top-right corner, select `Expand PVC` and enter a new value.
    • Documented as Known Issue

    Attachments

      Issue Links

        Activity

          People

            rhn-support-rkieley Roderick Kieley
            mkrutov Mikhail Krutov
            Mikhail Krutov Mikhail Krutov
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: