4.1.8 release notes updates

Author: michaelklishin

release-notes/4.1.8.md

@@ -26,22 +26,36 @@ Release notes can be found on GitHub at [rabbitmq-server/release-notes](https://
 
    GitHub issue: [#15136](https://github.com/rabbitmq/rabbitmq-server/pull/15136)
 
- * `mirrored_supervisor:child/2` could fail with a `badmatch` exception
-   when a significant enough number of shovels (or federation links) was removed.
+  * [Default queue type](https://www.rabbitmq.com/docs/vhosts#default-queue-type) handling is now more defensive, avoiding an issue where
+   attempts to declare a queue in a virtual host without any DQT set would result
+   in a `PRECONDITION_FAILED` exception instead of falling back to the classic queue type
+   for DQT.
 
-   GitHub issue: [#15229](https://github.com/rabbitmq/rabbitmq-server/pull/15229)
+   GitHub issues: [#11541](https://github.com/rabbitmq/rabbitmq-server/issues/11541), [#12109](https://github.com/rabbitmq/rabbitmq-server/issues/12109), [#12821](https://github.com/rabbitmq/rabbitmq-server/issues/12821), [#13837](https://github.com/rabbitmq/rabbitmq-server/issues/13837)
 
  * Topic exchange binding deletions could leave orphaned trie edges in the Khepri projection,
    potentially causing a slowly creeping memory leak.
 
    GitHub issue: [#15025](https://github.com/rabbitmq/rabbitmq-server/pull/15025)
 
- * [Default queue type](https://www.rabbitmq.com/docs/vhosts#default-queue-type) handling is now more defensive, avoiding an issue where
-   attempts to declare a queue in a virtual host without any DQT set would result
-   in a `PRECONDITION_FAILED` exception instead of falling back to the classic queue type
-   for DQT.
+ * When a client that owns an exclusive queue disconnects and immediately reconnects and redeclares the same queue
+   (under the same name), RabbitMQ node could delete the new queue depending on the timing of events.
 
-   GitHub issues: [#11541](https://github.com/rabbitmq/rabbitmq-server/issues/11541), [#12109](https://github.com/rabbitmq/rabbitmq-server/issues/12109), [#12821](https://github.com/rabbitmq/rabbitmq-server/issues/12821), [#13837](https://github.com/rabbitmq/rabbitmq-server/issues/13837)
+   Previously the only workaround was to use exclusive server-named queues for clients that exhibited
+   this behavior. Now RabbitMQ nodes take internal owner identity into account and will remove
+   the original queue but not the new one.
+
+   GitHub issue: [#15276](https://github.com/rabbitmq/rabbitmq-server/pull/15276)
+
+  * "Other ETS" and "Other system" memory metrics could end up being reported as negative values
+    due to concurrent ETS table updates, deletion and creation on the node.
+
+    GitHub issue: [#15289](https://github.com/rabbitmq/rabbitmq-server/pull/15289)
+
+  * `mirrored_supervisor:child/2` could fail with a `badmatch` exception
+    when a significant enough number of shovels (or federation links) was removed.
+
+    GitHub issue: [#15229](https://github.com/rabbitmq/rabbitmq-server/pull/15229)
 
 
 ### Federation Plugins