Changes between Version 3 and Version 4 of MultipleInstancesOfGN


Ignore:
Timestamp:
Jan 14, 2011, 6:12:02 AM (13 years ago)
Author:
heikki
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MultipleInstancesOfGN

    v3 v4  
    1010 * Database inserts : Jeeves maintains an in-memory counter to create ids for database insertions. This should be changed, using an auto-inc type for the id column in the database (if this is supported in all DBMSs we support) or else by fetching latest id from the DB everytime before inserting.
    1111
    12  * uploaded files : Files uploaded with or to a metadata are stored on the filesystem of the instance where they are uploaded. This also affects logos, images used in harvesting, and codelists. You should configure both instances to use the same locations for this -- otherwise one of the instances can't retrieve uploaded files from the other. We'd need to check the code though, because files are stored in directories that are numbered, and we don't know off-hand if these numbers are also incremented in memory.
     12 * uploaded files : Files uploaded with or to a metadata are stored on the filesystem of the instance where they are uploaded. This also affects logos, images used in harvesting, and codelists. You should configure all instances to use the same locations for this -- otherwise one of the instances can't retrieve uploaded files from the other ones. We'd need to check the code though, because files are stored in directories that are numbered, and we don't know off-hand if these numbers are also incremented in memory.
    1313
    14  * site uuid : The site uuid is generated at startup. This should be changed to accommodate both instances to use the same site uuid, as it is 1 catalog from a user perspective.
     14 * site uuid : The site uuid is generated at startup. This should be changed to accommodate all instances to use the same site uuid, as it is 1 catalog from a user perspective.
    1515
    16  * harvesters : The harvesters would run in each instance, as they're defined in the DB. This would lead in one of the instances to a lot of failed inserts because of uuid restrictions. Best would be to add an instance-uuid parameter to the harvesters configuration, so they only run in the instance where they were defined.
     16 * harvesters : The harvesters would run in each instance, as they're defined in the DB. This would lead to a lot of failed inserts because of uuid restrictions. Best would be to add an instance-uuid parameter to the harvesters configuration, so they only run in the instance where they were defined.
    1717
    1818 * sticky session required : Because the editor function in GN uses an in-memory counter. This will be a problem if you don't use sticky sessions.