Request testing feedback for component/feature arbiter in release-3.10

[ShyamsundarR]

This issue tracks testing feedback on component/feature arbiter for release-3.10

Request the maintainer or person assigned to the issue to test and provide feedback on the health of the component before closing the issue.
NOTE: As a maintainer please change the assignment as needed, in case someone else is working on testing the component.

Other folks that are testing the release are also welcome to add tests performed to these issues, as that helps gauging the health of the component/feature.

Major points to look out for:

• We have introduced brick multiplexing, so tests with and without multiplexing enabled will help in understanding if there are any lingering issues
• readdir-ahead as a sub xlator to DHT is added with this release, this is an experimental feature, but testing with this enabled can help weed out any issues that other xlators may face when this feature is enabled
• If any upgrade or mixed mode cluster testing is performed, then testing out the glusterd changes to report op-version would be useful to perform

Check release notes to understand how to enable the above features: https://github.com/gluster/glusterfs/blob/v3.10.0rc0/doc/release-notes/3.10.0.md

This issue is tracked against the release-3.10 and will not appear in the project dashboard for the same, as this is a release activity and does not define scope for the release.

Happy testing!