View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000912 | unreal | ircd | public | 2003-04-22 14:56 | 2003-04-29 01:26 |
| Reporter | iceblade | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | open | ||
| Product Version | 3.2-beta15 | ||||
| Summary | 0000912: standby server links | ||||
| Description | What do you think of the idea that a server (leaf or hub)could use a standby link, example, now if a piece of the network is linked like : ServerA(leaf) - ServerB(hub) - ServerC(hub) - ServerD(leaf) now should server B is down (whatever reason), A will need to reconnect to C until that time, the server is normally split from the network But if A whould have had a backup link (already connected) to the second hub (C), and if that kicked in as soon as it noticed the link to B died, then leaf A whould have never been split from the rest of the network. This whould minimize impact to the users as soon as any hub should die (for whatever reason) of couse this whould mean that every leaf (and even hubs) have a second connection open, and ready to be used when nessecary Regards, Iceblade | ||||
| 3rd party modules | |||||
|
|
create autolink block to hub B & C in leafs config, and then use the deny link block to disallow link to one of them while the other one is still active in conf for A, linked to B (assuming your leaf connects to your hub, not from hub to leaf): link ServerB.ircnet.net { blah blah blah... options { autoconnect;} } link ServerC.ircnet.net { blah blah and again blah... options { autoconnect; } } deny link { mask ServerC.ircnet.net; rule directcon(ServerB.ircnet.net); type all; } Never used this thing, so don't know how it works exactly... just read the doc and writed this I think it won't cut the timeout between servers, and so users will see the split, but just after they'll see the other users coming back (the time needed by A to link to C) edited on: 04-22-03 16:20 |
|
|
This is way too complicated and I've thought of it a lot, the main problem is the messages are "out of order" while at IRC it's almost 100% of the time assumed everything is in sequence (ie: kick, rejoin.. not reverse). There have been some attempts to create such a thing, never looked at them but even IRC3 ("IRC3 is dead", "- stfu, thats not the topic now") doesn't know how to properly deal with all that.. In short: it's probably far too much trouble / time than it's worth, a quick relink would be lot easier and safer. Dunnow how it currently is, but maybe an option to DIRECTLY (or maybe within a few secs) relink to another server would be nice... without setting a connectionretry of 3s.. (something like that already exists, butd s,fkhkldh).. blah.. |
