| Smalyshev added a comment. |
The problem is as follows:
- Blazegraph stores the triples in BTree. Btree does have an ordering, and it is stable, but what is stored are not strings but terms generated from strings, which seem to be identified and ordered by essentially running ID - i.e. Term(1), Term(2), etc.
- Since different servers are loaded in different times from different dump/update combinations, same URIs/strings get different Term IDs - same URI may be Term(123) on one server and Term(3456) on another. This means order of the triples in indexes will be different on different servers.
- When paginating through results, different page requests may be directed to different servers, thus creating completely wrong picture in the summary data.
- Due to the way we do load balancing (IP-based kernel balancing) we can not ensure any request affinity, as the balancer does not even look inside the packets.
- Using client IP for balancing (pretty much the only thing we have that is not inside the packet) is not possible since we have varnish in front of LVS, which means client IPs are always the ones from Varnish servers. We do have real client IPs, but the are also inside the packets, so LVS can't use them.
TASK DETAIL
EMAIL PREFERENCES
To: Smalyshev
Cc: Smalyshev, Gehel, Aklapper, QZanden, EBjune, merbst, Avner, debt, D3r1ck01, Jonas, FloNight, Xmlizer, Izno, jkroll, Wikidata-bugs, Jdouglas, aude, Deskana, Manybubbles, Mbch331
Cc: Smalyshev, Gehel, Aklapper, QZanden, EBjune, merbst, Avner, debt, D3r1ck01, Jonas, FloNight, Xmlizer, Izno, jkroll, Wikidata-bugs, Jdouglas, aude, Deskana, Manybubbles, Mbch331
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
