Skip to main content
Version: Next(1.7.0)

Recommended Configuration

Linkis builds a layer of computing middleware between the upper application and the underlying engine. As an open source distributed computing middleware, it can be well deployed and run on Intel architecture servers and mainstream virtualization environments, and supports mainstream Linux operating system environments

1.1. Linux operating system version requirements

OSVersion
Red Hat Enterprise Linux7.0 and above
CentOS7.0 and above
Oracle Enterprise Linux7.0 and above
Ubuntu LTS16.04 and above

Note: The above Linux operating systems can run on physical servers and mainstream virtualization environments such as VMware, KVM, and XEN

Linkis supports 64-bit general-purpose hardware server platforms running on the Intel x86-64 architecture. The following recommendations are made for the server hardware configuration of the production environment:

Production Environment

CPUMemoryDisk typeNetworkNumber of instances
16 cores +32GB +SASGigabit network card1+

Note:

  • The above recommended configuration is the minimum configuration for deploying Linkis, and a higher configuration is strongly recommended for production environments
  • The hard disk size configuration is recommended to be 50GB+, and the system disk and data disk are separated

1.3. Software requirements

Linkis binary packages are compiled based on the following software versions:

ComponentVersionDescription
Hadoop3.3.4
Hive3.1.3
Spark3.2.1
Flink1.12.2
openLooKeng1.5.0
Sqoop1.4.6
ElasticSearch7.6.2
Presto0.234
PythonPython2

Note: If the locally installed component version is inconsistent with the above, you need to modify the corresponding component version and compile the binary package yourself for installation.

1.4. Client web browser requirements

Linkis recommends Chrome version 73 for front-end access

2. Common scenarios

2.1 Open test mode

The development process requires a password-free interface, which can be replaced or appended to linkis.properties

parameter namedefault valuedescription
wds.linkis.test.modefalseWhether to enable debugging mode, if set to true, all microservices support password-free login, and all EngineConn open remote debugging ports
wds.linkis.test.userhadoopWhen wds.linkis.test.mode=true, the default login user for password-free login

2.2 Login user settings

Apache Linkis uses configuration files to manage admin users by default, and this configuration can be replaced or appended to linkis-mg-gateway.properties. For multi-user access LDAP implementation.

parameter namedefault valuedescription
wds.linkis.admin.userhadoopadmin username
wds.linkis.admin.password123456Admin user password

2.3 LDAP Settings

Apache Linkis can access LDAP through parameters to achieve multi-user management, and this configuration can be replaced or added in linkis-mg-gateway.properties.

parameter namedefault valuedescription
wds.linkis.ldap.proxy.urlNoneLDAP URL address
wds.linkis.ldap.proxy.baseDNNoneLDAP baseDN address
wds.linkis.ldap.proxy.userNameFormatNone

2.4 Turn off resource checking

Apache Linkis sometimes debugs exceptions when submitting tasks, such as: insufficient resources; you can replace or append this configuration in linkis-cg-linkismanager.properties.

parameter namedefault valuedescription
wds.linkis.manager.rm.request.enabletrueresource check

2.5 Enable engine debugging

Apache Linkis EC can enable debugging mode, and this configuration can be replaced or added in linkis-cg-linkismanager.properties.

parameter namedefault valuedescription
wds.linkis.engineconn.debug.enabletrueWhether to enable engine debugging

2.6 Hive metadata configuration

The public-service service of Apache Linkis needs to read hive metadata; this configuration can be replaced or appended in linkis-ps-publicservice.properties.

parameter namedefault valuedescription
hive.meta.urlNoneThe URL of the HiveMetaStore database.
hive.meta.usernoneuser of the HiveMetaStore database
hive.meta.passwordNonepassword for the HiveMetaStore database

2.7 Linkis database configuration

Apache Linkis access uses Mysql as data storage by default, you can replace or append this configuration in linkis.properties.

parameter namedefault valuedescription
wds.linkis.server.mybatis.datasource.urlNoneDatabase connection string, for example: jdbc:mysql://127.0.0.1:3306/dss?characterEncoding=UTF-8
wds.linkis.server.mybatis.datasource.usernameNoneDatabase user name, for example: root
wds.linkis.server.mybatis.datasource.passwordNoneDatabase password, for example: root

2.8 Linkis Session cache configuration

Apache Linkis supports using redis for session sharing; this configuration can be replaced or appended in linkis.properties.

parameter namedefault valuedescription
linkis.session.redis.cache.enabledNoneWhether to enable
linkis.session.redis.host127.0.0.1hostname
linkis.session.redis.port6379Port, eg
linkis.session.redis.passwordNonepassword

2.9 Linkis module development configuration

When developing Apache Linkis, you can use this parameter to customize the database, Rest interface, and entity objects of the loading module; you can modify it in linkis-ps-publicservice.properties, and use commas to separate multiple modules.

parameter namedefault valuedescription
wds.linkis.server.restful.scan.packagesNonerestful scan packages, for example: org.apache.linkis.basedatamanager.server.restful
wds.linkis.server.mybatis.mapperLocationsNoneMybatis mapper file path, for example: classpath:org/apache/linkis/basedatamanager/server/dao/mapper/.xml
wds.linkis.server.mybatis.typeAliasesPackageNoneEntity alias scanning package, for example: org.apache.linkis.basedatamanager.server.domain
wds.linkis.server.mybatis.BasePackageNoneDatabase dao layer scan, for example: org.apache.linkis.basedatamanager.server.dao

2.10 Linkis module development configuration

This parameter can be used to customize the route of loading modules during Apache Linkis development; it can be modified in linkis.properties, and commas are used to separate multiple modules.

parameter namedefault valuedescription
wds.linkis.gateway.conf.publicservice.listcs,contextservice,data-source-manager,metadataQuery,metadatamanager,query,jobhistory,application,configuration,filesystem,udf,variable,microservice,errorcode,bml,datasource,basedata -managerpublicservice services support routing modules

2.11 Linkis file system and material storage path

This parameter can be used to customize the route of loading modules during Apache Linkis development; it can be modified in linkis.properties, and commas are used to separate multiple modules.

parameter namedefault valuedescription
wds.linkis.filesystem.root.pathfile:///tmp/linkis/Local user directory, a folder named after the user name needs to be created under this directory
wds.linkis.filesystem.hdfs.root.pathhdfs:///tmp/HDFS user directory
wds.linkis.bml.is.hdfstrueWhether to enable hdfs
wds.linkis.bml.hdfs.prefix/apps-datahdfs path
wds.linkis.bml.local.prefix/apps-datalocal path