> After few round of stress testing I got this output on one fastrouter,
> this
> time it did not lock itself into infinite loop it's just that statis
> output
> got repeated keys:
>
> { "version": "1.0-dev-1734",
> "uid": 0,
> "gid": 0,
> "cwd": "/",
> "fastrouter": ["127.0.0.1:2500"],
> "subscriptions": [
> { "key": "app1.domain.com",
> "hits": 3128,
> "nodes": [
> {"name": "172.16.200.56:3001", "modifier1": 0,
> "modifier2": 0, "last_check": 1322582298, "requests": 1564, "tx":
> 10414588,
> "ref": 0, "death_mark": 0},
> {"name": "172.16.200.55:3001", "modifier1": 0,
> "modifier2": 0, "last_check": 1322582298, "requests": 1564, "tx":
> 10440952,
> "ref": 0, "death_mark": 0}
> ]
> },
> { "key": "pingapp.local",
> "hits": 2514,
> "nodes": [
> {"name": "172.16.200.55:3000", "modifier1": 0,
> "modifier2": 0, "last_check": 1322582290, "requests": 15, "tx": 510,
> "ref":
> 0, "death_mark": 0},
> {"name": "172.16.200.56:3000", "modifier1": 0,
> "modifier2": 0, "last_check": 1322582291, "requests": 13, "tx": 442,
> "ref":
> 0, "death_mark": 0}
> ]
> },
> { "key": "app2.domain.com",
> "hits": 0,
> "nodes": [
> {"name": "172.16.200.56:3002", "modifier1": 0,
> "modifier2": 0, "last_check": 1322582291, "requests": 0, "tx": 0, "ref":
> 0,
> "death_mark": 0}
> ]
> },
> { "key": "pingapp.local",
> "hits": 6,
> "nodes": [
> {"name": "172.16.200.55:3000", "modifier1": 0,
> "modifier2": 0, "last_check": 1322582260, "requests": 4, "tx": 136, "ref":
> 0, "death_mark": 0},
> {"name": "172.16.200.56:3000", "modifier1": 0,
> "modifier2": 0, "last_check": 1322582261, "requests": 2, "tx": 68, "ref":
> 0, "death_mark": 0}
> ]
> },
> { "key": "app2.domain.com",
> "hits": 0,
> "nodes": [
>
>
>
> {"name": "172.16.200.56:3002", "modifier1": 0,
> "modifier2": 0, "last_check": 1322582261, "requests": 0, "tx": 0, "ref":
> 0,
> "death_mark": 0}
>
> ]
>
>
>
> }
>
>
>
> ]
I have committed another series of fix/optimizations.
- nodes marked as dead will be skipped even if their reference is > 0
(only already accepted request will continue)
- added another check in auto-opmtized-list consistence (i suppose this is
the one throwing your error)
- a potential segmentation fault in slot removal should be fixed
Let me know if it definitely fix it for you
--
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
