Resolved Issues in 5.1.0-SP45

Prev Next

Cluster Expansion

  • ORION-204266: Improved handling of BMC firmware versions to eliminate an issue that could cause a BMC matching query does not exist error when trying to add a Mavericks MLK DBox to the cluster.

Networking

  • ORION-206544: Updated OpenSM configuration validations to avoid raising a Wrong OpenSM configuration alert in case the configuration has been manually changed to one that is different from the default.

  • ORION-203521: Improved NIC link rate validations to avoid generating a false internal nics rate speed is not aligned alarm.

Element Store

  • ORION-207892: Resolved an issue which could cause the cluster to encounter a assertion failed: (eres != EStoreRes::OK) ranges_to_mark not empty alert followed by denylisting @handle=<handle> as traversal_type=19 resulted with res=PERSISTENT_ERROR and then locally denylisting shard_type=0 shard_id=<shard> as op=DELETE_ELEMENT resulted with res=28 deny list alerts.

  • ORION-206865: Enhanced Alternate Data Stream (ADS) handling to eliminate a flow that could result in a CNode container restart with the assertion failed: (!at_least_one_generation_taken) at least one generation type is taken by this fiber or an ancestor fiber in context that expects error.

  • ORION-204314: Introduced improvements to avoid write latency spikes after massive write operations.

NFS

  • ORION-211906: Made updates to ensure there is no performance degradation when processing some specific NFS workload types.

Replication

  • ORION-213476: Updated replication initial synchronization routines to resolve an issue that could cause multiple allocated 90% of mooktze buffers! top consumer is REPLICATION_INIT_NAME_CONTENT_LOOKUP_TREE and assertion failed: (success) Failed write locking an RWSpinlock for 100000 times- couldn't finalize the write lock alerts on the cluster.

  • ORION-210898: Introduced enhancements to prevent errors caused by timeouts when using S3 replication for a very large number of S3 users.

  • ORION-204928: Resolved an issue that could cause a false clone_id=1000065870 is MISSING but should have existed alarm associated with a previously deleted replication stream.

Authentication & Authorization

  • ORION-188575: Updated LDAP lookup logic to allow for querying user groups where the group DN does not have the dc= string specified. Prior to this change, such queries were blocked, resulting in access deny errors when using OpenLDAP authentication.

VMS

  • ORION-193437: Fine-tuned VMS worker and task management timeouts to avoid a flow that could cause VMS tasks to hang and, in some cases, could result in a VMS restart.

Platform & Control

  • ORION-214262: Resolved an issue that could cause multiple CNode containers to restart with the assertion failed: ((stack_size_left) > (0)) (-5184 > 0) Stack overflow! error.

  • ORION-208889: Resolved an issue that could occur while copying data from an S3 bucket snapshot and cause CNode containers to restart with the assertion failed: (handle.clone_id == DEFAULT_CLONE_ID) Clones are not supported for temp refs error.

  • ORION-208753: Resolved an issue where CNode containers could get restarted following a switch failure due to which one of the interfaces on each node went down.

  • ORION-207363: Updated cluster HA routines to prevent a flow where deactivation of a DNode for a BMC firmware upgrade could cause temporary service disruption.