Hi, We have been experiencing catastrophic (database-corrupting) failures with our new OWLIM-SE 4.3 triplestore this week, and I am sure this must be down to a bad setup or configuration, or possibly the way in which our application uses OWLIM-SE.
The relevant infrastructure is: - Windows 8 64-bit server with 24Gb RAM & 28Gb hard disk - OWIM-SE 4.3 in Sesame RDF on Tomcat 7 running with Xmx=16Gb On this environment we are hoping to run four triplestores with the same characteristics: - roughly 25 million statements - roughly 3-4 million entities - hundreds of graphs These sizes will only grow over time (in particular we anticipate having lots of additional smallish graphs being added over time). Currently the triplestores are each configured with: - no reasoning - 10,000,000 entity index size - no predicate or FTS index, but PCSOT and PTSOC indexes - 250m cache memory, all on tuple index memory The application accessing the triplestore performs multiple simultaneous queries *and updates* each second. My particular questions about this set-up are: * are there any known issues with running OWLIM-SE on Windows? * are there any known issues with running OWLIM-SE within Tomcat 7? * is it foolish to run more than one triplestore on a given Tomcat instance? * does the entity index size look about right (to enable growth)? * is the tuple index memory too small? * how is tuple index memory managed with multiple triplestores within Tomcat? * are there any known issues with OWLIM-SE and simultaneous updates? * would using OWIM-Enterprise provide a more robust environment? Given our experience with these bad crashes this week, we are obviously concerned about backing up (and restoring) the data we have within the triplestores. As far as I'm aware we have the following options: * shutting down Tomcat, copying the repository directory and restarting Tomcat (causing interruption to service for several minutes of shutdown/copy/startup time) * extracting data at regular intervals which can then be re-loaded when necessary for restoring (increasing query load on the server and application logic to ensure inclusion of last-modified statements on graphs) Are there any other backup options with OWIM-SE? Many thanks in advance for your help, Jeni -- Jeni Tennison http://www.jenitennison.com _______________________________________________ OWLIM-discussion mailing list [email protected] http://ontotext.com/mailman/listinfo/owlim-discussion
