You can do this by adding the following lines to /etc/security/limits. To persist through a reboot these should be set in /etc/nf or a file in the /etc/sysctl.d directory: _keepalive_time=200Ī user named looker in the group named looker to run the Looker application.Ī ulimit for the looker user of 4096 or higher. If Looker instance and Redshift cluster are within the same VPC, If Looker detects that the MTU setting is greater than 1500 during a database connection test, it displays the following error: MTU of network interface eth0 is too large (> 1500). For more information about this setting, see the Configuring the MTU of an instance section of this Amazon Web Services article. If Looker is connecting to AWS Redshift from an AWS VCP private network, you must set the MTU to 1500. If users require API access, you must allow inbound traffic to your Looker instance through TCP port 19999. You must allow inbound traffic to your Looker instance through TCP port 9999. Libssl and a libcrypt.so must be present on the system. Note: We recommend that you start Looker with the JVM flag -Dnashorn.args=-optimistic-types=false when running Looker under JDK11. Other versions of Java, Oracle JDK, and OpenJDK are not supported at this time. In addition, Looker recommends that you transition to new Java updates as they are released. Looker recommends the JDK, instead of the JRE, to take advantage of the extra troubleshooting tools. Looker uses OpenJDK (version 11) for performance and memory usage improvements. Looker is supported only on Linux versions with 圆4 instruction sets. However, we support Looker on release versions of all major enterprise Linux distributions, including RedHat, CentOS, and Amazon Linux. We use Ubuntu Linux (LTS releases) for our internal Looker hosting, and we recommend it for customers who do not have a Linux preference.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |