cancel
Showing results for 
Search instead for 
Did you mean: 
Administration & Architecture
Explore discussions on Databricks administration, deployment strategies, and architectural best practices. Connect with administrators and architects to optimize your Databricks environment for performance, scalability, and security.
cancel
Showing results for 
Search instead for 
Did you mean: 

Databricks report error: unexpected end of stream, read 0 bytes from 4 (socket was closed by server)

SolaireOfAstora
New Contributor

Has anyone encountered this error and knows how to resolve it?

"Unexpected end of stream, read 0 bytes from 4 (socket was closed by server)."

This occurs in Databricks while generating reports.

I've already adjusted the wait_timeout to 28,800, and both and net_write_timeout to 31,536,000 (the maximum values) on the database side (MySQL).

Are there any other configurations I should modify, either on the database side or in Databricks?

0 REPLIES 0