Additional info: RHCS 3.0 Content Plan:
According to development, users should not have to make any changes. However, we do support both simple and asynchronous messaging types. Additionally, we support the POSIX transport type. Documentation covers undocumented ms_type, ms_type_public, ms_type_cluster, and ms_async... settings.
See https://gitlab.cee.redhat.com/red-hat-ceph-storage-documentation/doc-Red_Hat_Ceph_Storage_3-Configuration_Guide/commit/2657011dc9794f19a95c5e49aaba00b69da38bcf for details.
Removed the fine-grained async setting for now due to lack of feedback from engineering on the recent comments. Ceph uses these features whether we like it or not. The setting content is from upstream and contains tuning information.
My conversation with Josh is that people should not have to set ms_type, but we agreed to document it anyway.
Sylesh, per #1, see: https://gitlab.cee.redhat.com/red-hat-ceph-storage-documentation/doc-Red_Hat_Ceph_Storage_3-Configuration_Guide/commit/5019f7ac25e18346d1429d4da784d506886b9f10
Reverted comment 9. Received feedback directly from Sage, and made changes accordingly. See
With the foregoing changes, the added ms_type content and settings will remain for 3.0.