You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems to be an issue related to the pred_contrib=True handling in the C library itself: in the lightgbm4j library we have an issue with concurrent prediction crashing the whole JVM process due to the call not being thread-safe. See issue metarank/lightgbm4j#88 for details and a reproducer.
Description
I'm using the model behind a gRCP prediction service. The service predicts one example at a time.
I can reproduce the bug locally like
The error is like
or
or
depending on different runs.
max_workers=1
, the error seems to go away.pred_contrib=True
, the error seems to go away, so it lookspredict
alone is thread-safe, consistent with Is the function "LGBM_BoosterPredictForMat" thread safe? #666Reproducible example
I can produce some diff error, but also related to threading using the following code:
The error is like
or
Environment info
LightGBM version or commit hash:
lightgbm==3.3.2
Command(s) you used to install LightGBM
I'm using lightgbm inside a monorepo with bazel, but I think under the hood it's equivalent to
python -m pip install lightgbm
Additional Comments
The text was updated successfully, but these errors were encountered: