Changes between Version 5 and Version 6 of LoadBalanceable

Timestamp:

Mar 22, 2012, 12:32:22 PM (12 years ago)

Author:

heikki

Comment:

--

LoadBalanceable

@@ -64 +64 @@
 The current implementation is in effect a form of pessimistic locking (concurrent edit sessions cannot successfully save), with additional disadvantage that the users are not informed when they start editing that they will lose their changes. This will be replaced by a more direct form of pessimistic locking, making it impossible to open a metadata for editing if it is being edited already at that moment. Admin functions will be available to force unlock metadata.
 
+=== settings ===
+When settings are modified from one GN node, the other nodes will be out of date because the settings are kept in memory from startup. To prevent this we propose two alternatives: 
+
+ * no longer keep the settings in memory, but look them up everytime. This costs a bit more DB selects of course, but with an index on the unique column these simple selects should not take too long. This would also allow us to delete !SettingManager, which we have wanted to do for a long time.
+ * alternatively, a second update-broadcast to the peer nodes can instruct them to re-initialize !SettingManager.
+
+Your opinions on this are welcome.