Yes, due to the incorrect tagging of the 2.1.0.1, 2.1.0.2, and 2.1.0.3 versions, for this one you should go by branch.
Then it is pretty much confirmed that the problem is the timeout.
I checked the changelog again, and sure enough, the timeout code was introduced in 2.1.0.3.
@tejus if you follow the github issue for this problem, the suggestion is to set --read-write-timeout=5m to expand it a bit, or --read-write-timeout=0 to disable it completely.
Setting it to 0 should make it behave the same as 2.1.0.2, but I would like to get confirmation that this workaround fixes the problem.