Page History
...
Content layer | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Now, proceed to edit /etc/cassandra/default.conf/cassandra.yaml sudo nano /etc/cassandra/default.conf/cassandra.yaml
The first items we will be editing relate to the IP address of the Cassandra node and communications settings. In our diagram above, this IP address is 192.168.130.10. You will need to search for 3 keys in the configuration file and modify them accordingly. The seeds parameter is a comma-delimited list containing all of the seeds in the Cassandra cluster. Since our cluster consists of only the single node, it contains only one entry - our IP address. The other 2 parameters contain the IP address on which Cassandra listens for connections and the IP address to broadcast to other Cassandra nodes in the cluster. The broadcast_rpc_address may be commented out using a # character. If so, remove the "#" and make sure there are no leading spaces. Additionally, we need to set rpc_address to 0.0.0.0 (meaning, it will listen to rpc requests on all interfaces), and start_rpc to true (so it will process rpc requests).
The next set of parameters control thresholds to ensure that the data being sent is processed properly.
If you have installed your commit log in its own partition, the default commit log size will be the lesser of ¼ of the partition size or 8GB. In order to ensure that the recommended 8GB is used, you must uncomment the commitlog_total_space_in_mb, such that it will show as below. However, if you are uncommenting this value, please ensure that the partition has enough space to accommodate an 8GB commit log.
The next step is to point the data to the new locations. There are 4 entries which will be modified: data_file_directories, commitlog_directory, hints_directory, and saved_caches_directory. Search for these keys and edit them as follows:
After you have made these changes, save the cassandra.yaml file. Now, start the related services, as follows: systemctl start cassandra Now, proceed to check if Cassandra is running. To do this, issue the following command: nodetool status If the service is running, you will receive output such as below: Datacenter: datacenter1=======================Status=Up/Down|/ State=Normal/Leaving/Joining/Moving-- Address Load Tokens Owns (effective) Host ID RackUN 127.0.0.1 128.4 KB 256 100.0% ea3f99eb-c4ad-4d13-95a1-80aec71b750f rack1 If the service is fully operational, the first 2 characters on the last line will state "UN", indicating the node's status is Up, and its state is Normal. Tuning Linux for Cassandra Performance
There are multiple tunings that can be performed on Linux to improve the performance of Cassandra. The first step is to configure the TCP settings by adding the following tuning parameters to /etc/sysctl.conf file: net.core.rmem_max=16777216 To apply the setting without requiring a reboot issue the command: # sysctl -p For a full list of steps to take to tune Linux, go to: Installing Teamwork CloudInitial InstallationThe deployment script for TWCloud (install_twc2021x_centos7.sh) creates a twcloud user, under which the service will run, and downloads all of the necessary files and executes the installer. Before running the script, download TWCloud installer file, twcloud_2021x_installer_linux64.bin, and place it in the same location as the script.
When you are installing TWCloud
Next, the TWCloud's Pre-Installation Summary will appear. It should look as follows:
Post-Install ConfigurationThe installer has created the preliminary configuration of TWCloud. There are a few more changes, which we must make to the various configurations files in order for TWCloud to be fully functional.
ExecStart=/opt/local/TeamworkCloud/scripts/linux/twcloud-run To start the authserver service, execute the following command sudo systemctl start authserver To start the teamwork cloud service, execute the command sudo systemctl start twcloud To start the webapp service, execute the command sudo systemctl start webapp To ensure the services start on reboot, execute the following commands sudo systemctl enable twcloud sudo systemctl enable authserver sudo systemctl enable webapp Additional information which may affect installations in restricted environmentsLog FilesTWCloud executes under the twcloud user, and by default will store log files of Teamwork Cloud and Authserver under this user's profile (/home/twcloud). There are 2 configuration files which control the location of these log files:
In this file, there are settings for 2 log files which must be edited. <appender name="SERVER-FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"><file>${user.home}/.twcloud/2021x/server.log</file><rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy"><fileNamePattern>${user.home}/.twcloud/2021x/server.%d{yyyy-MM-dd}.%i.log.zip</fileNamePattern><maxFileSize>50MB</maxFileSize><totalSizeCap>1024MB</totalSizeCap></rollingPolicy><encoder><pattern>%-5.5level %date{YYYY-MM-dd HH:mm:ss.SSS} %message [%logger{200}, %thread{10}]%n</pattern></encoder></appender><appender name="SERVER-STARTUP-CONFIG-FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"><file>${user.home}/.twcloud/2021x/startup-config.log</file><rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy"><fileNamePattern>${user.home}/.twcloud/2021x/startup-config.%d{yyyy-MM-dd}.%i.log.zip</fileNamePattern><maxFileSize>50MB</maxFileSize><totalSizeCap>1024MB</totalSizeCap></rollingPolicy><encoder><pattern>%-5.5level %date{YYYY-MM-dd HH:mm:ss.SSSXXX} %message %n</pattern></encoder></appender> In each section, there are 2 settings which must be modified: file and fileNamePattern. The first setting (file) controls the absolute path to the latest log file. The second setting (fileNamePattern) controls the naming convention for the archiving of the log files. In most cases, it will suffice to replace the ${user.home} token with a different location, but you must ensure that the twcloud user has ownership of the target directories.
This file contains one section which must be modified. <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"><file>${user.home.dir}/.authserver/2021x/authserver.log</file><rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"><fileNamePattern>${user.home.dir}/.authserver/2021x/authserver.%i.log.zip</fileNamePattern><minIndex>1</minIndex><maxIndex>10</maxIndex></rollingPolicy><triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"><maxFileSize>30MB</maxFileSize></triggeringPolicy><encoder><pattern>%-5.5level %date{YYYY-MM-dd HH:mm:ss.SSS} %message [%logger{0}, %thread{10}]%n</pattern></encoder></appender> The same changes and permissions apply to the changes to this file as to those for /opt/local/TeamworkCloud/configuration/logback.xml. Files installed on system locations
Frequently Asked QuestionsQ: When accessing https://ip_address:8443/webapp I am displayed with a Tomcat 404 errorA: This error is typically caused by incorrect credentials for the authentication of webapp. This is accompanied by recurring error messages in web-app.log. 2019-10-12 14:49:14,625 [main] INFO com.nomagic.webappplatform.internal.version.TWCVersionValidator - Waiting for TWC/AuthServer to start, 120 of 120 Verify that the credentials are correct in webappplatform.properties Q: When Accessing the Teamwork Cloud Admin Console (webapp), I get a system error when redirected to the Authserver login screen A: This error is typically caused by an omission of the referring URL in the authetication server's whitelist, authentication.redirect.uri.whitelist, located in authserver.properties. You will see a corresponding error in authserver.log. ERROR 2019-10-04 17:26:52.258 AuthorizeException: invalid_request, Invalid redirect_uri parameter [AuthorizeController, …] Update the whitelist to include the referring URL. A common cause is accessing webapp via a server name of FQDN, when the wyitelist only contains entires for the IP address. Q: After entering my credentials in the Authserver login screen, I am not logged in, no error is displayed, and I am presented once again with the login screen A: This error is typically caused by a mismatch in the client secret entries - authentication.client.secret located in authserver.properties and webappplatform.properties, and pswd (esi.console.client.pswd) in application.conf. You will see a corresponding error in authserver.log ERROR 2019-10-04 17:30:49.382 Invalid client secret … |
...