The Client File Service (CFS) stores and distributes files needed by TSM (e.g. certificates, customization files, etc.). Files that are managed by the Client File Service are renamed and obfuscated before they are distributed across the deployment. This process also parametrizes the file attributes that are required by Tableau services. As a result, files are not mapped to a single file location on the file system. Be sure you have an off-box backup of all files managed by CFS.
The following files are managed by CFS:
The following files are not managed or distributed by CFS:
The Client File Service functions much like the File Store does for files needed by business services. By default, CFS is only installed on the initial node of your Tableau Server installation. To configure CFS to for high availability, we recommend that you configure an instance of CFS on each of the nodes where you deploy the Coordination Service.
In a cluster, if a node that is running your only instance of CFS fails, any files being managed by CFS will be lost, and you will need to repopulate CFS those files by reimporting certs and custom images, and making any related configuration changes.
ProcessClient File Service
Status Status of the Client File Service process is not visible on the Status Page. Use the TSMÂ CLI to view status. For more information, see View Server Process Status Logging Logs generated by the the Client File Service process are located in/var/opt/tableau/tableau_server/data/tabsvc/logs/clientfileserviceWhat happens when a CFS process fails? Nothing, as long as there is still at least one functioning CFS process in the cluster. The controller will redirect file transfer requests to the other working CFS process.
Failed Client File Service processes automatically restart as long as the computer itself is otherwise healthy.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4