The cluster data contains the hash of the secure cookie key and the communication protocol (http, https, or https no verify). Only one load balancing cluster can exist per database, and this cluster is defined by the first node that comes online within the cluster. Please note that Local Launcher sessions are enabled by default. When using Launcher Sessions, see additional requirements under Launcher considerations. If you have previously run Workbench with a SQLite database, it is strongly advised that you execute the database Migration to the PostgreSQL database first. Workbench must be configured to use a PostgreSQL database, and an empty database must be present for Workbench to write important cross-node state. See the Shared storage section for additional details. See Using Amazon EFS with Posit Team).Īn explicit server-wide shared storage path also must be defined. User home directories must be accessible via shared storage (e.g., all nodes mounting the same NFS volume or Amazon EFS. The clocks on all nodes must be synchronized. The same applies for any groups used by Workbench users, and also to the Workbench service user account, rstudio-server. User accounts must be accessible from each node and usernames and user ids must be identical on all nodes. Server configurations (i.e. contents of the /etc/rstudio directory) must be identical, with the exception of options related to the address of each node ( There are several requirements for nodes within Posit Workbench clusters:Īll nodes must run the same version of Posit Workbench.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |