bogdan: I think if the shared file system would be required just for attachments, it wouldn't need to be very fancy. I think OTRS doesn't modify what it has already written on disk for articles / attachments. So it only does reads and additional writes. No editing.
It does rely on a consistent view of what files exist in a directory on all nodes; that’s the thing that drives the cluster filesystem requirement. Another reason we moved to the transactional approach with the DMS. bogdan: I'm certain they have. Right now, my installation is not monstrous. It will handle ~30 agents and 100 daily tickets. For a while, I hope I'll be able to keep things in check with a single app server node. The bigger problem is that I have to get it off the ground with a db injected with 75000 tickets, 200000 articles and 1000 customer accounts from our custom legacy system. But I also want to be prepared for "unexpected success" and that's why I ask about load balancing. If that comes to be, maybe I'll have the budget for official support. Even in the simple configuration, the Linux-HA stuff might be worth looking at. It’s pretty impressive to kill the primary server and watch the other node pretty much assume the position without human intervention. 8-)
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
