| ID | Description |
|---|---|
| 41068 | A node could crash when powering up from an abrupt failure in the rare case where the volume containing the most recently written data is deleted just before an NVMe device failure, and also the system completes the full rebuild before any new writes are issued to any volume replicated on that node. If this occurs, the remediation is to either fail the node in place or contact Lightbits Support, who can perform an internal procedure to recover the node from this state. |
| 40883 | In the specific case of using VCP to upgrade a cluster, the upgrade to Lightbits version 3.17.1 or higher will fail because VCP cannot parse the new version format. To successfully upgrade the cluster, use the Lightbits core CLI or REST API directly. |
| 38826 | In-Band Authentication: setting the trusted-host-secret command with the host/target secret specified and not in a proper format is accepted and will result in an authentication failure. |
| 38497 | When creating a new server to replace another server in the cluster (using the --extend-cluster=false flag - note that this is also the default), the new server will not participate in all proper distribution of replicas over the cluster and could cause an imbalance of resources. |
| 38496 | Creating a new server to replace another server in the cluster (using the --extend-cluster=false flag - note that this is also the default) - while dynamic rebalance is enabled - could cause the new server to participate in the dynamic rebalance process. The nodes on the server could then move automatically to active and not remain unattached. This prevents the server from acting as a replacement in the replace node process. |
| 37830 | A node could fail to return to active state, if in some rare cases a data integrity error occurs during the power-up process. |
| 37544 | discovery-client could crash when network connectivity to the cluster is disrupted concurrently with volume changes triggering a notification from the discovery service. After such a crash, the discovery-client service is automatically restarted. |
| 37505 | The volume statistic 'physicalOwnedCapacity' might report an incorrect value when data is overwritten at the same LBA block with a different length. This can occur when the overwritten data is compressed with a different compression ratio than the original. In such cases, the length of the overwritten data is not accounted for in the statistic. |
| 32827 | When TRIM is enabled and a user performs the discard operation, the logical report size might be incorrect and not reflect the true logical size. |
| 28027 | A server upgrade status will not update in the following sequence:
|
Was this page helpful?