-
arrgh. sorry, the above is mangled (it looked right in the preview).
2009-09-30 14:22:40 UTC by ken4
-
Hi,
I tried to build linx on a 64-bit ubuntu 9.04 system and it fails.
there are some obvious errors in some of the Makefiles, here is a (hopefully correct) patch:
<pre>
diff -Naur -x '*.o' linx-2.2.2/liblinx/Makefile linx-2.2.2.patched/liblinx/Makefile
--- linx-2.2.2/liblinx/Makefile 2009-06-10 08:20:09.000000000 -0400
+++ linx-2.2.2.patched/liblinx/Makefile 2009-09-29...
2009-09-30 14:03:38 UTC by ken4
-
Thanks for the input. We'll try to add this or a similar solution in the next Linx release (linx-2.3.0).
2009-09-15 06:55:09 UTC by tomkarls
-
I have completed my testing and it was a success. The connections are no longer dropped while true connection drop is detected within time given in parameters.
The following are the changes I did. It is done against 2.2.1. As you can see, I did not parametrize the setting, it is compiled in.
I hope you can include a solution like this in the official Linx distro, so we can drop this fix...
2009-09-10 22:40:54 UTC by paull7
-
I did not mention this, but of course the intent is to run multiple checks and ACK reqs within a single timeout interval. 2 should be the minimum to avoid problems like mine. I'm playing with 3 now.
2009-09-04 12:10:22 UTC by paull7
-
Modifying the reset value itself would be the minimum that solves the problem. It will however increase the timeout implicitly. E.g. if I say timeout is 3s and reset value is 3 (instead of current 2), the true timeout will be between 2*tmo and 3*tmo. So this goes against discovering dead nodes within timeout given in parameters.
What I think is needed is a different parameter: number of pings...
2009-09-04 12:08:17 UTC by paull7
-
This is a problem that was discussed when we developed the CM for Linx 2.2. On one hand "dead" nodes should be detected as soon as possible, on the other hand the connection should be robust. So we ended up with this compromise...
We didn't want to add too many configuration parameters, but would it be helpful if we made the reset value for the alive counter configurable via...
2009-09-04 08:19:21 UTC by tomkarls
-
In my tests I actually decided to go with 3 checks every timeout period. This protects us more against single network hit, esp. when timers drift.
It also reduces the true timeout range from today's conn_tmo - 2*conn_tmo (worst case is where last ping arrives right after a check, then conn_tmo later check is still good, then another check fails, but it has been 2*conn_tmo until then). The...
2009-09-03 15:56:05 UTC by paull7
-
First of all, many thanks for your support so far!
I have isolated a problem where rsyncing a lot of data from particular box causes it to drop Linx connections every now and then. The root cause was later narrowed down to high load and some packet loss combined, heavy rsync causes both at the same time.
Turns out Linx is allowing only one conn_tmo interval to pass without any ACK or ACK...
2009-09-03 14:40:33 UTC by paull7
-
It looks like a <stropts.h> has been included by mistake. My guess is that it was include for the ioctl prototype, which is wrong. We will remove the <stropts.h> header file in the next release. Thanks for input...
/Tommy.
2009-09-03 06:22:58 UTC by tomkarls
