Skip to content

Commit fffd688

Browse files
committed
rename dir
1 parent e6cb746 commit fffd688

File tree

1 file changed

+22
-22
lines changed

1 file changed

+22
-22
lines changed

faq/main.md

+22-22
Original file line numberDiff line numberDiff line change
@@ -15,72 +15,72 @@ Solution: jetty-servlet and jetty-security versions need to be upgraded from 9.3
1515

1616
Specific exception stack:
1717

18-
![linkis-exception-01.png](/Images/Tuning-and-Troubleshooting/linkis-exception-01.png)
18+
![linkis-exception-01.png](/Images/tuning-and-troubleshooting/linkis-exception-01.png)
1919

2020
Solution: jar package conflict, delete asm-5.0.4.jar;
2121

2222
#### Q3. When starting the microservice linkis-ps-datasource, JdbcUtils.getDriverClassName NPE
2323

2424
Specific exception stack:
2525

26-
![linkis-exception-02.png](/Images/Tuning-and-Troubleshooting/linkis-exception-02.png)
26+
![linkis-exception-02.png](/Images/tuning-and-troubleshooting/linkis-exception-02.png)
2727

2828

2929
Solution: caused by the Linkis-datasource configuration problem, modify the three parameters at the beginning of linkis.properties hive.meta:
3030

31-
![hive-config-01.png](/Images/Tuning-and-Troubleshooting/hive-config-01.png)
31+
![hive-config-01.png](/Images/tuning-and-troubleshooting/hive-config-01.png)
3232

3333

3434
#### Q4. When starting the microservice linkis-ps-datasource, the following exception ClassNotFoundException HttpClient is reported:
3535

3636
Specific exception stack:
3737

38-
![linkis-exception-03.png](/Images/Tuning-and-Troubleshooting/linkis-exception-03.png)
38+
![linkis-exception-03.png](/Images/tuning-and-troubleshooting/linkis-exception-03.png)
3939

4040
Solution: There is a problem with linkis-metadata-dev-1.0.0.jar compiled in 1.0, and it needs to be recompiled and packaged.
4141

4242
#### Q5. Click scriptis-database, no data is returned, the phenomenon is as follows:
4343

44-
![page-show-01.png](/Images/Tuning-and-Troubleshooting/page-show-01.png)
44+
![page-show-01.png](/Images/tuning-and-troubleshooting/page-show-01.png)
4545

4646
Solution: The reason is that hive is not authorized to Hadoop users. The authorization data is as follows:
4747

48-
![db-config-01.png](/Images/Tuning-and-Troubleshooting/db-config-01.png)
48+
![db-config-01.png](/Images/tuning-and-troubleshooting/db-config-01.png)
4949

5050
#### Q6, shell engine scheduling execution, the page reports Insufficient resource, requesting available engine timeout, eneningeconnmanager linkis.out, and the following error is reported:
5151

52-
![linkis-exception-04.png](/Images/Tuning-and-Troubleshooting/linkis-exception-04.png)
52+
![linkis-exception-04.png](/Images/tuning-and-troubleshooting/linkis-exception-04.png)
5353

5454
Solution: The reason Hadoop did not create /appcom/tmp/hadoop/workDir. Create it in advance through the root user, and then authorize the Hadoop user.
5555

5656
#### Q7. When the shell engine is scheduled for execution, the engine execution directory reports the following error /bin/java: No such file or directory:
5757

58-
![shell-error-01.png](/Images/Tuning-and-Troubleshooting/shell-error-01.png)
58+
![shell-error-01.png](/Images/tuning-and-troubleshooting/shell-error-01.png)
5959

6060
Solution: There is a problem with the local java environment variables, and you need to make a symbolic link to the java command.
6161

6262
#### Q8, hive engine scheduling, the following error is reported EngineConnPluginNotFoundException:errorCode:70063
6363

64-
![linkis-exception-05.png](/Images/Tuning-and-Troubleshooting/linkis-exception-05.png)
64+
![linkis-exception-05.png](/Images/tuning-and-troubleshooting/linkis-exception-05.png)
6565

6666
Solution: It is caused by not modifying the version of the corresponding engine during installation, so the engine type inserted into the db by default is the default version, and the compiled version is not caused by the default version. Specific modification steps: cd /appcom/Install/dss-linkis/linkis/lib/linkis-engineconn-plugins/, modify the v2.1.1 directory name in the dist directory to v1.2.1 modify the subdirectory name in the plugin directory 2.1. 1 is 1.2.1 of the default version. If it is Spark, you need to modify dist/v2.4.3 and plugin/2.4.3 accordingly. Finally restart the engineplugin service.
6767

6868
#### Q9. After the linkis microservice is started, the following error is reported: Load balancer does not have available server for client:
6969

70-
![page-show-02.png](/Images/Tuning-and-Troubleshooting/page-show-02.png)
70+
![page-show-02.png](/Images/tuning-and-troubleshooting/page-show-02.png)
7171

7272
Solution: This is because the linkis microservice has just started and the registration has not been completed. Wait for 1~2 minutes and try again.
7373

7474
#### Q10. When the hive engine is scheduled for execution, the following error is reported: operation failed NullPointerException:
7575

76-
![linkis-exception-06.png](/Images/Tuning-and-Troubleshooting/linkis-exception-06.png)
76+
![linkis-exception-06.png](/Images/tuning-and-troubleshooting/linkis-exception-06.png)
7777

7878

7979
Solution: The server lacks environment variables, add export HIVE_CONF_DIR=/etc/hive/conf in /etc/profile;
8080

8181
#### Q11. When hive engine is scheduled, the error log of engineConnManager is as follows method did not exist: SessionHandler:
8282

83-
![linkis-exception-07.png](/Images/Tuning-and-Troubleshooting/linkis-exception-07.png)
83+
![linkis-exception-07.png](/Images/tuning-and-troubleshooting/linkis-exception-07.png)
8484

8585
Solution: Under the hive engine lib, the jetty jar package conflicts, replace jetty-security and jetty-server with 9.4.20;
8686

@@ -159,11 +159,11 @@ Solution: The reason is that there is a corresponding relationship between the v
159159

160160
#### Q15. When the python engine is scheduled, the following error is reported: Python proces is not alive:
161161

162-
![linkis-exception-08.png](/Images/Tuning-and-Troubleshooting/linkis-exception-08.png)
162+
![linkis-exception-08.png](/Images/tuning-and-troubleshooting/linkis-exception-08.png)
163163

164164
Solution: The server installed the anaconda3 package manager. After debugging python, two problems were found: (1) lack of pandas and matplotlib modules, which need to be installed manually; (2) when the new version of the python engine is executed, it depends on the higher version of python, first install python3, Next, make a symbolic link (as shown in the figure below) and restart the engineplugin service.
165165

166-
![shell-error-02.png](/Images/Tuning-and-Troubleshooting/shell-error-02.png)
166+
![shell-error-02.png](/Images/tuning-and-troubleshooting/shell-error-02.png)
167167

168168
#### Q16. When the spark engine is executed, the following error NoClassDefFoundError: org/apache/hadoop/hive/ql/io/orc/OrcFile is reported:
169169

@@ -215,43 +215,43 @@ Solution: cdh6.3.2 cluster spark engine classpath only has /opt/cloudera/parcels
215215

216216
#### Q17. When the spark engine starts, it reports queue default is not exists in YARN, the specific information is as follows:
217217

218-
![linkis-exception-09.png](/Images/Tuning-and-Troubleshooting/linkis-exception-09.png)
218+
![linkis-exception-09.png](/Images/tuning-and-troubleshooting/linkis-exception-09.png)
219219

220220
Solution: When the 1.0 linkis-resource-manager-dev-1.0.0.jar pulls queue information, there is a compatibility problem in parsing json. After the official classmates optimize it, re-provide a new package. The jar package path: /appcom/Install/dss- linkis/linkis/lib/linkis-computation-governance/linkis-cg-linkismanager/.
221221

222222
#### Q18, when the spark engine starts, an error is reported get the Yarn queue information excepiton. (get the Yarn queue information abnormal) and http link abnormal
223223

224224
Solution: To migrate the address configuration of yarn to the DB configuration, the following configuration needs to be added:
225225

226-
![db-config-02.png](/Images/Tuning-and-Troubleshooting/db-config-02.png)
226+
![db-config-02.png](/Images/tuning-and-troubleshooting/db-config-02.png)
227227

228228
#### Q19. When the spark engine is scheduled, it can be executed successfully for the first time, and if executed again, it will report Spark application sc has already stopped, please restart it. The specific errors are as follows:
229229

230-
![page-show-03.png](/Images/Tuning-and-Troubleshooting/page-show-03.png)
230+
![page-show-03.png](/Images/tuning-and-troubleshooting/page-show-03.png)
231231

232232
Solution: The background is that the architecture of the linkis1.0 engine has been adjusted. After the spark session is created, in order to avoid overhead and improve execution efficiency, the session is reused. When we execute spark.scala for the first time, there is spark.stop() in our script. This command will cause the newly created session to be closed. When executed again, it will prompt that the session is closed, please restart it. Solution: first remove stop() from all scripts, and then execute the order: execute default.sql first, then execute scalaspark and pythonspark.
233233

234234
#### Q20, pythonspark scheduling execution, error: initialize python executor failed ClassNotFoundException org.slf4j.impl.StaticLoggerBinder, as follows:
235235

236-
![linkis-exception-10.png](/Images/Tuning-and-Troubleshooting/linkis-exception-10.png)
236+
![linkis-exception-10.png](/Images/tuning-and-troubleshooting/linkis-exception-10.png)
237237

238238
Solution: The reason is that the spark server lacks slf4j-log4j12-1.7.25.jar, copy the above jar and report to /opt/cloudera/parcels/CDH-6.3.2-1.cdh6.3.2.p0.1605554/lib/spark/jars .
239239

240240
#### Q21, pythonspark scheduling execution, error: initialize python executor failed, submit-version error, as follows:
241241

242-
![shell-error-03.png](/Images/Tuning-and-Troubleshooting/shell-error-03.png)
242+
![shell-error-03.png](/Images/tuning-and-troubleshooting/shell-error-03.png)
243243

244244
Solution: The reason is that the linkis1.0 pythonSpark engine has a bug in obtaining the spark version code. The fix is ​​as follows:
245245

246-
![code-fix-01.png](/Images/Tuning-and-Troubleshooting/code-fix-01.png)
246+
![code-fix-01.png](/Images/tuning-and-troubleshooting/code-fix-01.png)
247247

248248
#### Q22. When pythonspark is scheduled to execute, it reports TypeError: an integer is required (got type bytes) (executed separately from the command to pull up the engine), the details are as follows:
249249

250-
![shell-error-04.png](/Images/Tuning-and-Troubleshooting/shell-error-04.png)
250+
![shell-error-04.png](/Images/tuning-and-troubleshooting/shell-error-04.png)
251251

252252
Solution: The reason is that the system spark and python versions are not compatible, python is 3.8, spark is 2.4.0-cdh6.3.2, spark requires python version<=3.6, reduce python to 3.6, comment file /opt/cloudera/parcels/CDH/ The following lines of lib/spark/python/lib/pyspark.zip/pyspark/context.py:
253253

254-
![shell-error-05.png](/Images/Tuning-and-Troubleshooting/shell-error-05.png)
254+
![shell-error-05.png](/Images/tuning-and-troubleshooting/shell-error-05.png)
255255

256256
#### Q23, spark engine is 2.4.0+cdh6.3.2, python engine was previously lacking pandas, matplotlib upgraded local python to 3.8, but spark does not support python3.8, only supports below 3.6;
257257

0 commit comments

Comments
 (0)