- 23 Aug, 2010 2 commits
-
-
Vincent Pelletier authored
Also, factorises packet creation. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2214 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2213 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
- 20 Aug, 2010 1 commit
-
-
Vincent Pelletier authored
onConnectionClosed is already called inside Connection.close() when peer is identified (via setOnClose). Calling it here would trigger an exception as it verifies that _connection is set before un-setting it. As a replacement, verify that _connection is not set when Connection.close() returns (so onConnectionClosed was actually called). git-svn-id: https://svn.erp5.org/repos/neo/trunk@2212 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
- 19 Aug, 2010 10 commits
-
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2211 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2210 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
It is possible for rid not to be in partition_dict or new_partition_dict, as this method is called from a master notification (partition changed), which might happen outside of any replication (so when both dicts are empty). git-svn-id: https://svn.erp5.org/repos/neo/trunk@2209 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2208 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2207 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2206 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2205 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2204 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2203 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2202 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
- 04 Aug, 2010 10 commits
-
-
Grégory Wisniewski authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2201 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2200 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2199 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2198 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
The replicator must be stopped to avoid storages request unfinished transactions to the master while it is not able to answer. This prevent from considering the storage as broken. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2197 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2196 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
If a client connect to a storage more than one time, cut the old connection and replace it by the new one. This is required if the client reconnect to fast and the storage handle in single poll loop the new connection *then* the lost of the previous connection. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2195 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
The only purpose on this is to have the log in setHandler() that display the connection's UUID instead of None. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2194 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2193 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2192 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
- 12 Jul, 2010 6 commits
-
-
Grégory Wisniewski authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2191 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2190 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
Avoid duplicates in deployment configurations. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2189 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
With a sample configuration for supervisor. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2188 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
About the potential use of twisted framework. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2187 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
Since the last OID used (in a transaction) is synchronized with the storages, it is no more required to restart a NEO cluster after an import. Remove the related message. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2186 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
- 21 Jun, 2010 6 commits
-
-
Grégory Wisniewski authored
- A storage is not operational while connecting to the primary master - A storage is not ready until connected to a primary master, with an operational partition table and fully initialized. The 'ready' attribute must be initialized to False when PrimaryFailure or OperationFailure exceptions are reaised to prevent acceptation of incoming clients (see storage/handlers/identification.py that check app.ready value) git-svn-id: https://svn.erp5.org/repos/neo/trunk@2185 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2184 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2183 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2182 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2181 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
- The storages no more check the last OID during a store - The storages inconditionnaly store the last OID notified by the master - The master check during the if a greater oid was used by a client - The master always notify the last OID when a pool is generated or if the check above is True - The master's transaction manager manager the last oid and oid generator git-svn-id: https://svn.erp5.org/repos/neo/trunk@2180 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
- 18 Jun, 2010 4 commits
-
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2179 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2178 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2177 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
This fix an issue where some locks were not released on a storage because the node list used to sent abort notifications was built with the content of data_dict that don't keep informations about unresolved conflicts. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2176 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
- 17 Jun, 2010 1 commit
-
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2175 71dcc9de-d417-0410-9af5-da40c76e7ee4
-