3 ms·
Thanks for the pointers! Unfortunately, I don't think this applies. I'm certainly not getting this behavior - I wouldn't have even thought of it if I haven't ob
by drdaeman 10y ago
Thanks for the pointers! Unfortunately, I don't think this applies. I'm certainly not getting this behavior - I wouldn't have even thought of it if I haven't observed higher latencies resulting from (sub)requests chain jumping from node to node back-and-forth, instead of staying within the node's boundaries.
The problem is, the network space there is flat, not hierarchical - while I haven't looked at the actual implementation code, I believe container addresses are just randomly chosen from a single big 10.42/16 subnet and I'm unaware if there's a way that I can assign hosts, say, a /20 out of that space (yes, this would've solved things nicely).
- bboreham 10y agoOh. Right. I happen to work on a different Docker network, which 'chunks' the address space so containers on the same machine are very likely to have contiguous addresses. Hadn't occurred to me theirs doesn't do that.
- drdaeman 10y agoJust curious - what networking/clustering solution you're using? (I'm asking, so the next time I'll have to make a choice between stacks I would be more aware about the finer details.) Thanks!
- bboreham 10y agoI work on Weave Net http://github.com/weaveworks/weave http://github.com/weaveworks/weave.