instal the new version for windows Sticky Previews 2.9

Resolution: Portworx now cleans up the mountpath even when the application is not found on the node. User Impact: Portworx didn't clean up the mountpaths where the volume had previously been attached, as it couldn't locate the application on the local node. When an application pod using an FA Direct Access volume was failed over to another node, and Portworx was restarted on the original node, the pod on the original node became stuck in the Terminating state. Resolution: Portworx now creates NFS proxy volumes successfully without restarting the Portworx service. User Impact: Although NFS proxy volumes were created, the service restart affected user applications. When NFS proxy volumes were created, it resulted in the restart of the Portworx service. Resolution: The timeout for queued attach requests has been increased to 15 minutes for FA DirectAccess volumes. When Portworx received a high volume of requests to attach FA DirectAccess volumes, the queue for these attach requests gradually grew over time, leading to a panic in Portworx. This was because an FA attach operation involved making REST API calls to FA, as well as running iSCSI rescans, which consumed more time. User Impact: Portworx would restart on the node. If an attach request remained in the processing queue for a long time, it would lead to a panic.

Resolution: Portworx now forces a full backup in scenarios where the previous cloudsnap node is down. User Impact: The most recent snapshots were lost. The minimum duration for refresh is one minute.Ĭloudsnaps of an aggregated volume with a replication level of 2 or more uploaded incorrect data if one of the replica nodes from which a previous cloudsnap operation had been executed was down. Pxctl cluster options update -fb-stats-expiry-duration Users can now configure the default duration, which is set to 15 minutes, after which the logs should be refreshed to get the most up-to-date statistics for FlashBlade volumes, using the following command:: These stale devices had no direct impact but could have led to slow operations if many were present. Portworx now removes stale FlashArray multipath devices upon startup, which may result from pod failovers (for FlashArray Direct Access) or drive set failovers (for FlashArray Cloud Drives) while Portworx was not running. Improved how Portworx identifies pods with volumes in the Read-Only state before restarting them.ĬSI sidecar images are updated to the latest open source versions. Portworx has upgraded or enhanced functionality in the following areas: Improvement Number

Instal the new version for windows Sticky Previews 2.9