[BUG] JVM can not exit.
qumingxing opened this issue · 6 comments
Describe the bug
Spark JVM can not exit after running Spark SQL
2023-06-08 14:43:47,249 [INFO] [PDClient-update-leader-pool-0] try update leader (org.tikv.common.PDClient(org.tikv.common.PDClient.tryUpdateLeader:641)) 2023-06-08 14:43:57,249 [INFO] [PDClient-update-leader-pool-0] try update leader (org.tikv.common.PDClient(org.tikv.common.PDClient.tryUpdateLeader:641)) 2023-06-08 14:44:07,249 [INFO] [PDClient-update-leader-pool-0] try update leader (org.tikv.common.PDClient(org.tikv.common.PDClient.tryUpdateLeader:641)) 2023-06-08 14:44:07,278 [INFO] [serviceSafePoint-thread-0] register service GC safe point 442028814641398319 success. (com.pingcap.tispark.safepoint.ServiceSafePoint(com.pingcap.tispark.safepoint.ServiceSafePoint.$anonfun$new$1:52)) 2023-06-08 14:44:17,249 [INFO] [PDClient-update-leader-pool-0] try update leader (org.tikv.common.PDClient(org.tikv.common.PDClient.tryUpdateLeader:641)) 2023-06-08 14:44:27,249 [INFO] [PDClient-update-leader-pool-0] try update leader (org.tikv.common.PDClient(org.tikv.common.PDClient.tryUpdateLeader:641)) 2023-06-08 14:44:37,249 [INFO] [PDClient-update-leader-pool-0] try update leader (org.tikv.common.PDClient(org.tikv.common.PDClient.tryUpdateLeader:641)) 2023-06-08 14:44:47,249 [INFO] [PDClient-update-leader-pool-0] try update leader (org.tikv.common.PDClient(org.tikv.common.PDClient.tryUpdateLeader:641)) 2023-06-08 14:44:57,249 [INFO] [PDClient-update-leader-pool-0] try update leader (org.tikv.common.PDClient(org.tikv.common.PDClient.tryUpdateLeader:641))
Spark and TiSpark version info
Spark：v3.2.1
TiSpark: v3.2.2
TiDB: v6.5.2
This issue is stale because it has been open for 30 days with no activity.
the same problem
it should be fixed in #2698 and published as tispark v3.2.2
Can you confirm the version of your tispark
This issue is stale because it has been open for 30 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.
This issue was closed because it has been inactive for 14 days since being marked as stale.