Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

【Question】catboost for spark how to exit #2151

Closed
chencjiajy opened this issue Aug 21, 2022 · 7 comments
Closed

【Question】catboost for spark how to exit #2151

chencjiajy opened this issue Aug 21, 2022 · 7 comments
Assignees

Comments

@chencjiajy
Copy link

chencjiajy commented Aug 21, 2022

Problem: catboost for spark application not exit after finished, it hangs....., spark.stop() not work。 how to make the application exit after training. (ps:both IDEA and spark-submit not exit)
catboost version:1.0.6

example

how to exit catboost for spark

@shuchih
Copy link

shuchih commented Dec 8, 2022

same problem here

@minhdang241
Copy link

I got the same problem? is there any work around guys ? :/

@tqtensor
Copy link

We have the same problem.

@art777nn
Copy link

We have the same problem.

Tried to run different versions catboost-spark:
catboost-spark_3.4_2.13:1.2.2, 1.2, 1.2.1
catboost-spark_3.4_2.12:1.2.2, 1.2, 1.2.1

Context:
Kubernets 1.27.7
Spark 3.4.2
Scala 2.13 or 2.12
Catboost 1.2.2
PySpark 3.4.2

Driver does not stop after fit call.

Attached extended logs that are an output after the python script is completed. You can see that at the end of logs PoolingHttpClientConnectionManager attempts to close idle connections infinitely.

Log line output:
PoolingHttpClientConnectionManager: Closing connections idle longer than 60000 MILLISECONDS
log_catboost.txt

@andrey-khropov andrey-khropov self-assigned this Jan 26, 2024
@andrey-khropov
Copy link
Member

andrey-khropov commented Feb 15, 2024

Fixed in 2cdb8a2, the good news is that is was just auxiliary threads not shut down at the end of the program execution, the main computation logic had not been affected, the training results should be valid.

@art777nn
Copy link

Fixed in 2cdb8a2, the good news is that is was just auxiliary threads not shut down at the end of the program execution, the main computation logic had not been affected, the training results should be valid.

Thank you! This commit cured the application! Can you please tell me when we can expect a patch in maven?

@andrey-khropov
Copy link
Member

Can you please tell me when we can expect a patch in maven?

This week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants