| ID | Description |
|---|---|
| 39211 | When deleting the most recent snapshot of a volume while a node holding a replica is offline, recently written data could revert to the data stored in that snapshot if the node later becomes the primary. |
| 39168 | When using DCPMM, if a snapshot is taken after an abrupt failure, recently written data could be reverted to the state captured in the snapshot. |
| 22995 | discovery-client init-connection does not specify a timeout. In case of a failure in a discovery service on one of the targets, discovery-client might not abort the faulty discovery-service connection and will not fail over to another functioning service. |
| 22994 | Discovery-client does not time out on submission/completion of NVMe commands, if they never get a response from the discovery-service. |
| 22993 | Discovery-client fails to update referrals and cache entries when getting a list of bad entries. |
| 21415 | In some cases, the actual QoS (beta) bandwidth limit may be lower than its configured value. |
Was this page helpful?