Page Comparison

...

• OSS Updates

  • The irqbalance daemon is updated to 1.1.0. (SWAR-7159)

  • Intel Network Driver updates include igb 5.3.5.4, ixgbe 4.4.0-k, ixgbevf 3.2.2, bnx2x 1.712.30-0, hpsa 3.4.16-0, and mpt2sas/mpt3sas 13.100.00.00. (SWAR-7160)

  • The Linux kernel is updated to 4.8.11. (SWAR-7126)

• Improvements

  • The User-Agent header on requests that result in 400, 500, or 501 response codes is logged. This helps administrators identify the client application generating the errant requests. (SWAR-6828)

  • Swarm allows an unlimited number of parts in a multipart upload. This was previously restricted to a maximum of 10,000. (SWAR-6056) 

  • Statistics on various search query types and features are collected. These statistics are published via SNMP, REST, and the health report. (SWAR-6731)

  • Chunked transfer-encoded writes are optimized so they are less likely to generate excessive trapped space requiring defragmentation. (SWAR-7239)

  • Swarm supports the definition of multiple Elasticsearch host targets for Historical Metrics in the metrics.target setting. Additionally, a new alias, metrics.targets, exists for this setting. (SWAR-7085)

  • The Metrics Curator supports definition of multiple Elasticsearch host targets for Historical Metrics. In the metrics.cfg file, the "host" parameter accepts a comma-delimited set of Elasticsearch server addresses. The "hosts" parameter is a synonym for the original "host" parameter. (SWAR-7063)

  • Per-object feed errors no longer logged at the critical severity and so do not change the node state to 'error' if they occur. Continue to monitor the Dashboard (or legacy console Feeds page) for blocked feeds. (SWAR-7282)

  • Rename performance of erasure-coded objects within buckets is significantly improved. (SWAR-7271)

  • Statistics on the number of read or write requests closed prematurely by clients are tracked. This can help administrators identify misbehaving client applications. (SWAR-6783)

  • Swarm prevents cluster booting if the SNMP security administrator (read/write user) is not set properly in the configuration file. (SWAR-7137)

  • Disk light identification is improved and automatically chooses the best identification method based on the hardware. The included methods are: sg_ses, MegaCli64, sas2ircu, sas3ircu, and activity-based. End user modification of the plugin is discouraged unless a controller/driver not covered by these tools is used. (SWAR-7280)

  • How long uncleared error messages continue to appear in the Swarm Admin Console can be controlled. The new setting, console.messageExpirationSeconds, defaults to two weeks. (SWAR-6202)

  • A multipart COPY by part behaves operates like a multipart write complete, which sends back a an HTTP 202 response code and keep-alive characters to prevent client timeouts. (9.1.2: SWAR-7309)

• Resolved Issues

  • When using a replication feed that restricts certain storage domains from replication, the feed can incorrectly cause all context objects (domains, buckets), but not the objects contained within them, to be replicated to the remote cluster. Contact DataCore Support for assistance before deleting them if these empty contexts exist in a cluster. (SWAR-7100)

  • A Swarm node reports the "ok" state before the volumes are mounted. (SWAR-7323)

  • During creation of a Search Feed index in 9.0.1, a race condition caused the error "unsupported operand type(s) for *: 'NoneType' and 'int'". Swarm automatically retries affected objects, so the error can be ignored. (SWAR-7226)

  • During rolling upgrade and rolling reboot involving 9.0.x releases, critical log messages reported attempts to contact rebooting nodes. (SWAR-7317)

  • Dynamic changes to the SNMP password prevented subsequent successful reboot. (SWAR-7136)

  • ElasticSearchMetricsPusher unexpected exception errors occur during the upgrade process when metrics data is being preserved. (SWAR-7294)

  • Emergency defragmentation is performed on disks without sufficient trapped space to warrant the effort. (SWAR-7079)

  • Failures in attempts to look up host IP addresses at boot time slowed the overall boot process. (SWAR-7269)

  • The Linux kernel mpt2sas driver's prot_mask option is set to 1. This overrides the driver's default Protection Information (T10-PI) setting because it can cause problems in disk arrays containing non-PI-enabled disks. (SWAR-7372)

  • An issue with the Metrics Curator is fixed whereby an incorrect configuration can lead to an invalid Elasticsearch mapping during initial setup. If a persistent "Data unavailable" message is observed on the interface and HTTP POST "400" errors in a browser's JavaScript console, this situation exists. Contact DataCore Support for the corrective actions. (SWAR-7332)

  • Completed FVR/ECR recoveries are not remembered for a retired or failed volume left in the cluster after a reboot. (SWAR-7326)

  • Storage rebalancing can stop before reaching an optimal balance in some clusters after the addition of new capacity. (SWAR-7246)

  • Interfaces reported some nodes as offline rather than in maintenance mode during a reboot of a multi-node chassis. (SWAR-7318)

  • Swarm may not recognize a blank disk if several are hot-plugged in quick succession. (SWAR-7225)

  • Corrected an issue in disk encryption and hot-plug incorrectly mapping storage volumes in a chassis containing more than 10 disks. (SWAR-7381)

  • Disk serial numbers and firmware information is not displayed for encrypted volumes. (SWAR-7223)

  • Swarm Metrics did not publish SCSP 404 count statistics. (SWAR-7350)

  • When an EC object is renamed and another object is present in the former name, the renamed object may have segments reclaimed by the health processor, resulting in data loss. (9.1.2: SWAR-7445)

  • The newname query argument did not properly handle non-ASCII characters, resulting in a successful rename to the incorrect name. (9.1.2: SWAR-7408)