This article briefly introduces the general upgrade process for versions above 1.0.3
linkis -> /appcom/Install/LinkisInstall/linkis-1.1.3.20220615210213
https://linkis.apache.org/docs/x.x.x/release
and the version release-note: https://linkis.apache.org/download/mainPress Deployment guide document (the installation of the management console in the document can be skipped) to install the new version.
When installing the service, if the historical data is retained, please retain the historical data, if you do not need to retain the data, just reinstall it directly
Do you want to clear Linkis table information in the database? 1: Do not execute table-building statements 2: Dangerous! Clear all data and rebuild the tables other: exit Please input the choice: ## choice 1
After the service installation is completed, the database structure needs to be modified, including table structure changes and table data changes
Find the corresponding version db/upgrade/x.x.x-schema/
sql change file
If it is executed across multiple versions, please execute them in the order of versions, If some versions do not have x.x.x_schema (after the linkis>=1.1.0 version, as long as the adjustment of the database table is involved, there will be a corresponding version of the schema file), it means that there is no change in the data table in this version
├── linkis_ddl.sql # The current version of the full ddl database definition language table building statement ├── linkis_dml.sql # The current version of the full dml data manipulation language data additions and changes └── upgrade ├── 1.1.0_schema # The corresponding version of sql │ └── mysql │ ├── linkis_ddl.sql │ └── linkis_dml.sql ├── 1.1.1_schema │ └── mysql │ ├── linkis_ddl.sql │ └── linkis_dml.sql └── 1.1.3_schema └── mysql └── linkis_ddl.sql
#If it is executed across multiple versions, please execute in order of versions, execute ddl first and then execute ddl #For example, currently upgrade from linkis-1.0.3 to linkis-1.1.2 source upgrade/1.1.0_schema/mysql/linkis_ddl.sql source upgrade/1.1.0_schema/mysql/linkis_dml.sql source upgrade/1.1.1_schema/mysql/linkis_ddl.sql source upgrade/1.1.1_schema/mysql/linkis_dml.sql
According to the actual situation, decide whether to make the following adjustments
Authentication for interface calls yes 1.1.1 Version adjustment Migrate the original TOKEN configuration from ${LINKIS_HOME}/conf/token.properties
to the database table linkis_mg_gateway_auth_token
, For the TOKEN originally configured in token.properties
, you need to manually migrate the table
1.1.1 supports the functions of UDF multi-version control and UDF storage to BML, the table structure stored by UDF functions has been adjusted, and the historical data of UDF needs to be migrated separately
In version 1.1.1, the key of the session field was adjusted from bdp-user-ticket-id
-> to linkis_user_session_ticket_id_v1
, If it is an upgrade to Linkis. At the same time, DSS or other projects are deployed, but in their service lib package, the linkis-module-x.x.x.jar package of Linkis that they depend on is <1.1.1, you need to modify the file located in ${LINKIS_HOME}/conf/linkis.properties
echo "wds.linkis.session.ticket.key=bdp-user-ticket-id" >> linkis.properties
1.1.1 Begin to adjust the default cluster name of yarn queue wds.linkis.rm.cluster
sit is adjusted to default, if you have been using sit, please modify the table data Cluster name in linkis_cg_rm_external_resource_provider
If there is a third-party appconn plugin installed in ${LINKIS_HOME_OLD}/lib/linkis-engineconn-plugins
in the previous version of Linkis, you need to copy it to the new version, It is best to link to the appconn path through a soft chain like:
#Check if the old version has a third-party appconn installed cd ${LINKIS_HOME_OLD}/lib/linkis-engineconn-plugins/ ll appconn -> /appcom/Install/LinkisInstall/appconn #The new version is consistent cd ${LINKIS_HOME}/lib/linkis-engineconn-plugins/ #soft chain ln -snf /appcom/Install/LinkisInstall/appconn appconn
If dss is installed in the original version, you need to copy the dss-gateway-support-x.x.x.jar
in the original package to the ./lib/linkis-spring-cloud-services/linkis-mg-gateway/
directory of linkis like:
cp ${LINKIS_HOME_OLD}/lib/linkis-spring-cloud-services/linkis-mg-gateway/dss-gateway-support-1.1.3.jar ${LINKIS_HOME}/lib/linkis-spring-cloud-services/linkis- mg-gateway/dss-gateway-support-1.1.3.jar
To upgrade the backend, you also need to upgrade the corresponding management console resources. You don't need to install the management console, just replace the static resources directly.
Upload it to the server where the management console is located, and decompress it
tar -xvf apache-linkis-x.x.x-incubating-web-bin.tar.gz
There are many ways to upgrade the management console, because it is only the update of resources, which can be done through the installation script of the management console, or it can directly overwrite the original resources. It is recommended to use the soft chain method, just modify the target address of the soft chain. The following takes the new version resource path method as an example
The nginx configuration file is by default in /etc/nginx/conf.d/*
nginx log files are in /var/log/nginx/access.log
and /var/log/nginx/error.log
Scenario 1: If it is integrated into the DSS project, modify the address of the linkis management console resource in the DSS project to point to The nginx configuration file for dss is by default in /etc/nginx/conf.d/dss.conf
#Example server { ...... location dss/linkis { alias /appcom/Install/linkis-web-newversion/dist; # static file directory index index.html index.html; } ..... }
Scenario 2: If linkis is deployed independently Modify the configuration of Nginx, the static resource address points to the new version of the linkis console Linkis' nginx configuration file is by default in /etc/nginx/conf.d/dss.conf
#Example server { ...... location dss/linkis { alias /appcom/Install/linkis-web-newversion/dist; # static file directory index index.html index.html; } ...... }
Reload nginx configuration
sudo nginx -s reload