~ctheune/gocept.zeoraid/trunk : changes

~ctheune/gocept.zeoraid/trunk » Changes from revision 165

From Revision 165 to 146

Rev	Summary	Authors	Tags	Date
165	add ZODB classifier add ZODB classifier	ctheune		13 years ago
164	Back to development: 1.0b9 Back to development: 1.0b9	ctheune		13 years ago
163	Preparing release 1.0b8 Preparing release 1.0b8	ctheune	1.0b8	13 years ago
162	document last changes document last changes	ctheune		13 years ago
161	Add new option 'fail-mode' to indicate whether the RAID shou... Add new option 'fail-mode' to indicate whether the RAID should be closed or turned read-only. Fixed shared blob support by re-implementing the noop support.	ctheune		13 years ago
160	Implement majority voting for results in co-op mode. This in... Implement majority voting for results in co-op mode. This included a lot of detailed changes that are reflected in the tests. (Sorry for the bulk check-in.)	ctheune		13 years ago
159	extract consistency check into separate method extract consistency check into separate method	ctheune		13 years ago
158	checkpoint: refactoring to introduce cluster modes checkpoint: refactoring to introduce cluster modes	tlotze		13 years ago
157	improved thread synchronisation to make tests more stable improved thread synchronisation to make tests more stable	tlotze		13 years ago
156	updated changelog updated changelog	tlotze		13 years ago
155	- made starting storage recovery atomic - made starting storage recovery atomic - keep tests from printing exceptions by solving thread ordering problems	tlotze		13 years ago
154	updated to newest ZODB 3.9 updated to newest ZODB 3.9	tlotze		13 years ago
153	pinned last package versions known to work pinned last package versions known to work	tlotze		13 years ago
152	License and copyright cleanup. License and copyright cleanup.	ctheune		14 years ago
151	- #484437: Recipe handles address in zeo.conf incorrectly. W... - #484437: Recipe handles address in zeo.conf incorrectly. When giving the ZEO address on the server only as a port that port would be ignored resulting in 127.0.0.1:8100 to be assumed for the management scripts. - #486217: Incomplete recoveries did not get cleared. Now the status output correctly displays 'degraded' after failed recoveries and the detailed status informs that the storage was degraded due to a failed recovery. Exception details are logged accordingly.	ctheune		14 years ago
150	- #484921: Further enhance logging output by also displaying... - #484921: Further enhance logging output by also displaying the name of the RAID storage involved. - Try forcing storages to close when they seemed to have failed opening. This is especially relevant for asynchronously connecting ZEO clients which otherwise continue to keep connecting but would never get picked up by ZEORaid.	ctheune		14 years ago
149	Back to development: 1.0b8 Back to development: 1.0b8	ctheune		14 years ago
148	Preparing release 1.0b7 Preparing release 1.0b7	ctheune	1.0b7	14 years ago
147	- #484921: Log reason why a backend is degraded. We also dis... - #484921: Log reason why a backend is degraded. We also display that reason in the detailed status of the controller client now. If an exception occured then we also log the traceback now. - Refactored protocol for displaying detailed status information of backend storages to be simpler, less error prone and easier to change in the future. - Fix little bug in status detail which would fail if the recovery status missed the transaction information bit.	ctheune		14 years ago
146	Re #484727: Document the issues with recovery in a multi-ZEO... Re #484727: Document the issues with recovery in a multi-ZEORaid setup.	ctheune		14 years ago

Older »