Closed michalkurka closed 5 years ago
@Pscheidl yes, this should be fixed in XGBoost but this will solve this issue for us. The only penalty we incur is when a multi-node model training is finished. This fixes issues with scoring regardless of the number of nodes because scoring in H2O is always single-node (per-chunk).
Makes me think we are good now.
@michalkurka Approved, definitely an improvement. Sleep deprivation is better to be avoided. :+1: :rofl: Are we waiting for dmlc/xgboost to provide the ultimate fix ?