@Amn_468 , Depends if you are receiving the file descriptor warning message across all the TS and if you happen to change the fds threshold across kudu Tserver roles then you should be doing in non prod hours or ensure no jobs are running. Please be informed that kudu doesnt offer rolling restart feature.

Service level config TS

CM->kudu->config->file descriptor for TS-> require all TS restart

However if the warning appears only for one specific TS and if you plan to change the thershold for one specific TS then it shouldnt cause any issue as its a distributed system and one worker role restart wont impact on your ongoing operations.

CM->kudu->instances->select the TS instance which throws the warning-> config-> set the fds value ->restart specific TS