summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* minor refactorbug23129Matthias Radestock2010-08-161-4/+1
|
* cosmeticMatthias Radestock2010-08-161-4/+3
|
* don't log file summary recover errorMatthias Radestock2010-08-151-8/+5
| | | | | the details aren't that important and get in the way of a fresh startup
* don't attempt to recover file summary when we know there isn't oneMatthias Radestock2010-08-151-4/+3
|
* cosmeticMatthias Radestock2010-08-151-4/+4
|
* more refactoringMatthias Radestock2010-08-151-17/+13
|
* yet more refactoringMatthias Radestock2010-08-151-35/+30
|
* now it compilesMatthias Radestock2010-08-151-12/+6
|
* minor refactorMatthias Radestock2010-08-151-12/+10
|
* cosmeticMatthias Radestock2010-08-151-1/+1
|
* minor refactorMatthias Radestock2010-08-151-1/+5
|
* Refactorings and improvents to msg_store startupMatthew Sackman2010-08-151-29/+39
|
* The underlying call to file:copy will not make use of any erlang-level read ↵Matthew Sackman2010-08-151-1/+1
| | | | buffer, so don't bother with it.
* Improve, correct and document msg store recoveryMatthew Sackman2010-08-151-19/+41
|
* Correct and simplify the recovery from crashed compactionsMatthew Sackman2010-08-151-101/+22
|
* When recovering, because of the possibility of finding the same msg twice, ↵Matthew Sackman2010-08-141-4/+5
| | | | ensure that we only count and include the first copy. Other copies are then ignored.
* A msg can appear > once in the same file because of multiple queues ↵Matthew Sackman2010-08-142-3/+5
| | | | receiving the same msg. When we iterate through the msgs we find in the file, we must check that the msg corresponds to the msg in the index, by matching not just with guid but also with offset. Also just for fun, assert the total_size matches. Also, fixed a mistake in file_handle_cache where the dirty flag on the destination of copy wasn't being set.
* bug 23118 merged into default (windows file descriptors limit)Marek Majkowski2010-08-130-0/+0
|\
* | Improvements to commentsbug23118Matthew Sackman2010-08-131-6/+10
| |
* | Reduce the file descriptor limit for Windows to 512Matthew Sackman2010-08-131-2/+2
|/
* merge bug23120 into defaultAlexandru Scvortov2010-08-132-6/+6
|\
| * tiny simplifying refactorMatthias Radestock2010-08-131-2/+1
| |
| * cosmetic: friendlier type nameMatthias Radestock2010-08-131-4/+5
| |
* | use consistent return types for start/start_link functionsbug23120Matthias Radestock2010-08-1321-34/+28
|/
* merge bug23095 into defaultMatthias Radestock2010-08-120-0/+0
|\
* \ Merging default into bug23095bug23095Matthew Sackman2010-08-121-10/+27
|\ \ | |/ |/|
| * do not ignore 'normal' permanent child terminations during shutdownMatthias Radestock2010-08-121-25/+31
| | | | | | | | | | | | | | | | | | If such a termination is worth reporting while the supervisor is running, it sure is still worth reporting when it's shutting down. This involves reverting all the changes related to ignoring normal termination during shutdown and instead adding some logic a bit higher up the call chain.
| * never ignore 'noproc' during shutdownMatthias Radestock2010-08-121-1/+0
| | | | | | | | | | | | We have no idea why the child died. Furthermore, we will only ever get this when a child has unlinked itself from the supervisor, which is naughty and shouldn't go unnoticed.
| * we must always clear both the 'EXIT' and 'DOWN' messageMatthias Radestock2010-08-121-7/+7
| |
| * cosmetic and minor refactoringMatthias Radestock2010-08-121-21/+15
| |
| * Prevent supervisor2 from getting upset if a child has already vanished ↵Matthew Sackman2010-08-101-10/+19
| | | | | | | | normally whilst the supervisor is trying to stop it
| * Modify behaviour of intrinsic to be more like transient, except in the case ↵Matthew Sackman2010-08-091-11/+6
| | | | | | | | of normal child exit
| * Reverting rabbit_sup to not use intrinsicMatthew Sackman2010-08-091-9/+9
| |
| * use state_del_child instead of remove_childMatthias Radestock2010-08-091-2/+2
| | | | | | | | remove_child removes child *specs* which is not what we want here
| * cosmeticMatthias Radestock2010-08-091-8/+7
| |
| * Convert rabbit_sup to supervisor2 using intrinsicMatthew Sackman2010-08-091-9/+9
| |
| * Introduce intrinsic restart typeMatthew Sackman2010-08-091-1/+16
| |
* | cosmeticMatthias Radestock2010-08-121-1/+3
| |
* | merge bug23104 into defaultMatthias Radestock2010-08-111-33/+89
|\ \
| * | remove redundant codebug23104Matthias Radestock2010-08-111-3/+2
| | |
| * | minor neatificationMatthias Radestock2010-08-111-3/+1
| | |
| * | merge default into bug23104Matthias Radestock2010-08-111-29/+88
| |\ \ |/ / /
| * | make table content spot check part of schema_integrity_checkMatthias Radestock2010-08-111-23/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | and - rename check_table_content to check_table_integrity - change wait_for_tables to only do what it says rather than also do the schema integrity check. This change is necessary in order to avoid an infinite recursion due to check_table_integrity needing to call wait_for_tables - add ensure_schema_integrity_check, which contains logic which previously was part of wait_for_tables - call wait_for_tables in all the right places, and no more
| * | idiot2Matthew Sackman2010-08-111-1/+0
| | |
| * | idiotMatthew Sackman2010-08-111-3/+1
| | |
| * | The table content tests need to happen *after* we've waited for the tables, ↵Matthew Sackman2010-08-111-7/+20
| | | | | | | | | | | | otherwise they can fail. Thus now two phases - schema checks, as before, and then table content checks.
| * | cosmeticMatthew Sackman2010-08-111-3/+3
| | |
| * | Improve match specsMatthew Sackman2010-08-111-11/+27
| | |
| * | Use match specs instead. This is a first pass - I want to be able to add ↵Matthew Sackman2010-08-111-35/+35
| | | | | | | | | | | | some guards and assert things a little more tightly
| * | Partial implementation of 3rd suggestion. Partial because I just wanted to ↵Matthew Sackman2010-08-101-9/+43
| | | | | | | | | | | | see the shape of it rather than implement the whole thing and then possibly have to revoke it. IMO, testing on the deep structure of terms is likely sufficient