DaskLGBMRegressor early_stopping_rounds error

[kunshouout]

It seems using early_stopping_rounds with DaskLGBMRegressor would result in
lightgbm.basic.LightGBMError: Socket recv error, Connection reset by peer (code: 104)

Is this expected behavior?

LightGBM version or commit hash:
3.3.5.99

[jameslamb]

Thanks for using LightGBM.

Early stopping is not yet supported in the Dask interface. You can follow #4189 to be notified if/when that support is added.

However... I wouldn't expect the error you mentioned could be caused by providing parameter early_stopping_rounds.

If you can provide us with enough information to reproduce the issue you're facing, we can help:

• operating system
• version of Python
• versions of dask and distributed
• minimal, self-contained code which reproduces the error

[github-actions]

This issue has been automatically closed because it has been awaiting a response for too long. When you have time to to work with the maintainers to resolve this issue, please post a new comment and it will be re-opened. If the issue has been locked for editing by the time you return to it, please open a new issue and reference this one. Thank you for taking the time to improve LightGBM!

[github-actions]

This issue has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this.