Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

MDS Tunables

Hello Admin,

I have a VM test cluster setup (3 node, 2 OSD per, 3.1.0) mostly to get a feel for the software and start learning ceph.  I was looking over the tunables area in the UI and didn't see any way to adjust MDS cache settings. I would like to increase the cache size along with adjust a few other parameters to see if they work in my use case.

Do I need to insert a line into the /etc/ceph/ceph.conf file or is there another file that controls different tunables for the cluster?

Thank you

From UI Configuration -> Ceph Configuration

Select mds section the Add

select key:  mds_cache_memory_limit

enter value (example) : 4G

Got it, Thank you.  I assume after changing the tunable that I would need to reboot the MDS server for the change to take affect?

I didn't see the add button in the configuration panel.

 

Out of curiosity, I was testing different failover cases with MDS nodes.

I started a windows file copy (8G file) to a cephfs share (open share, no AD.  2 public IP configured).  Midway through the transfer I disconnected one of the 2 configured MDS servers (1 active, 1 standby). I expected the file transfer to stop for a brief moment and then resume as CTDB fails over to the new active MDS server and the standby MDS node becomes active, however after checking that the CTDB status failed over successfully and that the standby MDS node had failed over successfully (ie, reported active), the windows transfer had not resumed.

Is this expected behavior when an MDS fails over?

Thank you,

The Add buttom is on top right of page, same row as Section and Category radio buttons. You do not need to restart.

HA in CIFS/SMB is limited, the client session reconnect in case of failures and failover but the existing i/o fails. This is a limitation compared to the other services. Its caused by Linux Samba server not fully supporting SMB version 3 which includes support for i/o recovery at the protocol level. In our release notes we recommend using Microsoft robocopy when copying files which includes application level recovery so it automatically resumes i/o in such failures, Samba do recommend using xcopy, but any application that handles i/o retries should be fine. For users doing manual copy from desktop, they need to retry the copy.

That is unfortunate to hear but I understand the limitation of Samba.

Thank you for the help and everything done on this project.