This page holds notes on the current Fedora configuration, as well as misc information that must be understood when configuring Fedora.
In order to run a large repository (more than 100k Fedora Objects) while using the ResourceIndex, you must have a 64-bit version of Java running on a 64-bit OS.
We will currently treat all Fedora-generated logs as disposable, being only useful for debugging. When we want to track "real" use, we will have to route everything through the Apache/Tomcat connnector. Fedora 2.2 should include more organized logging output, and we may switch to that system when it is available.
Ingest speedup – reduce garbage collection
From the Fedora mailing list comes this suggestion...
On Thu, 2006-01-26 at 16:07, Edwin Shin wrote:
> I don't recall the rationale for the gc on each commit, but it precedes
> 2.1b. If you're interested you could try settting the system property
> "fedora.GCOnCommit" to "false" (add it to fedora.sh).
Thanks a lot for that hint. We tried changing the setting and our speed
jumped from 3.1 obj/sec to 10.4 obj/sec (average over 5000 ingested
If this is a safe setting, then we'll keep it. We're using a dedicated
maschine for Fedora, so we don't need to minimize the amount of RAM used
by the JVM for Fedora.
Should anyone else want to try this, insert the line
in the exec-call under "# start Tomcat" in fedora.sh.
Fedora runs on its own (modified?) instance of Tomcat. It is currently not advisable to run anything besides Fedora on this version of Tomcat, because it has been tune to give some performance enhancements for Fedora use. Be very carful when selecting ports so they don't conflict with another Tomcat that may be running on the same machine. If you change the port on which Fedora runs, it will automatically reconfigure the Fedora Tomcat, since this is really the service that's running on that port. Certain types of changes to the Tomcat config are overwritten by Fedora, so it is unlikely that we could use this copy of Tomcat for anything else.
When making a change to an XSL file, there is no simple way to reset the cache, unless the behavior mechanism explicitly uses the clear-stylesheet-cache option. The only thing you can do is restart Fedora (which restarts Tomcat).
Bugs can be reported to Fedora's Bugzilla
user: fedora-bugreport at comm.nsdl.org