Resolution: Cluster-join failures now perform thorough cleanup to remove all temporary resources created during the failed cluster-join attempts.ĭuring migration, if a PVC has the sticky bit set (which prevents volumes from being deleted), it accumulated the internal snapshot that was created for the asynchronous DR deployment, thus consuming extra storage space. Incorrect allocation of floating license and insertion of excess data into the Portworx key-value database caused new nodes to repeatedly fail to join the Portworx cluster. This is improved, as Portworx do not create a fallback snapshot, allowing users to create clones from the last successful migrated snapshot if necessary for error cases.
In Async DR migration, a snapshot was previously created at the start of restores as a fallback in case of errors, but it added extra load with creation and deletion operations.
Instead, a warning message is displayed, advising customers to upgrade their multipath package. However, this prerequisite check has now been removed, and Portworx installs or upgrades are not blocked on these faulty versions. If a faulty version was detected, it was not possible to install or upgrade Portworx. In Portworx version 2.13.0, a prerequisite check was implemented to detect the versions of the multipath tool with known issues (0.7.x to 0.9.3) during installation or upgrade of Portworx. Recommends upgrading to version 2.13.3 due to the PWX-29074 issue, which is explained below. If you are currently using any Portworx 2.12 version, Portworx, Inc. Visit these pages to see if you’re ready to upgrade to the latest version: Portworx can now be deployed from Azure Marketplace with a pay-as-you-go subscription.Portworx by Pure Storage is proud to introduce the following new features: To enable this for all Portworx volumes, use the -ro-vol-pod-bounce all cluster option. This background task is enabled for FA DirectAccess volumes by default.
You can customize this time-interval with the -ro-vol-pod-bounce-interval cluster option. Resolution: A background task is now implemented to run periodically (by default every 30 seconds), which checks for read-only volumes and terminates managed pods using them. If any read-write volume changed to a read-only state, pods using these volumes had to be manually restarted to make the mounts back to read-write. Portworx has upgraded or enhanced functionality in the following areas: Improvement Number
0 kommentar(er)
