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
Given we have the opportunity to make some breaking changes in 1.0, I think we should remove the python based Rabit tracker, and only use the Scala based one. The reason for this is the Scala one has many more features, with things like timeouts.
@CodingCat in my experience, with issue 4628#issuecomment-510367032, the python tracker will just hang forever. But the Scala tracker will actually time out (Regardless of what we decide, we should investigate the 60sec issue)
Given we have the opportunity to make some breaking changes in 1.0, I think we should remove the python based Rabit tracker, and only use the Scala based one. The reason for this is the Scala one has many more features, with things like timeouts.
Here are some links:
At very least, we should default to the Scala one (given how much better it is) as a breaking change in 1.0.
The text was updated successfully, but these errors were encountered: