| That is what I have always assumed, if you look in the sessions table in the DB in the session_value column you can see that there is all of the user's configuration in one big string.
bogdan: Efficient and simple. I'm surprised. I assumed OTRS stores some user session data in memory/disk to process successive requests faster. | OTRS isn't that "clever" and certainly doesn't do versioning. Many tables are updated when the data is added to a ticket as it's not stored in one big flat table. bogdan: I imagined that when there's only one app server node some magic would prevent these race conditions and the magic would go away in a multi node config. Good to know there's no magic :). | Yep, but like I said there is nothing stopping you from doing it, but it does have it's drawbacks. Like David said if you are going to store this on disk then you will need to use a cluster filesystem, and I'm not entirely sure how this will work with multiple front end servers, hence why storing it in the DB (even given its "issues") would be the easier option as the frontend doesn't need to worry about being able to access the filesystem, it's all in the one place. 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 might be worth contacting OTRS support directly to see if they do have load balanced implementations and whether they would share any of the implementation details (can't help but to ask), but if you are going to have such a large installation anyway then it may be worthwhile taking out official support should you run into any issues with the implementation, at least then you are guaranteed help on the end of a phone. 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. Thanks, bogdan Steve > > --------------------------------------------------------------------- > 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 >
--------------------------------------------------------------------- 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
