Il giorno 24 feb 2017, alle ore 14:17, Peter Eckel <li...@eckel-edv.de> ha scritto: > Hi Luca, >> Of course you’d have problems during an actual failover (one backend fails >> or you manually take it out of the pool) but it should be a minor issue. > that's exactly the issue I'm trying to solve. My other solution (keeping the > sessions directory in sync) is quite clumsy, and I'm looking for the perfect > solution. Yeah many times we choose to simply ignore that because such events are rare and we prefer the bonus of keeping things simple, but of course every project is different and you should judge that by yourself (as I said never tried with IcingaWeb2 specifically, but we use to do that with other different web apps based on php or other languages).
The “perfect solution” is having sessions in sync, either keeping them local but synced or not having them local. In the php world afaik there is not a standardized solution to replicate session data (ie. like some solutions I’ve seen in java / tomcat that replicate session data using multicast traffic between all the backends) and I would rather not try to mess with the standard file-based sessions copying them back and forth. Usually you would go for the latter solution, having a centralized session store. Never tried, but you should be able to accomplish that using standard php session handlers (see http://php.net/manual/en/class.sessionhandler.php ) and IcingaWeb2 should just use what you configure. But then keep in mind Pascal’s notes about stuff that is neither in the user session nor in the database (announcements and dashboards)... -- Luca Lesinigo LM Networks Srl _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
