Age | Commit message (Collapse) | Author | |
---|---|---|---|
2011-08-16 | emulator: Add a fourth element in exception stacktraces | Björn Gustavsson | |
This commit is a preparation for introducing location information (filename/line number) in stacktraces in exceptions. Currently a stack trace looks like: [{Mod1,Function1,Arity1}, . . . {ModN,FunctionN,ArityN}] Add a forth element to each tuple that can be used indication the filename and line number of the source file: [{Mod1,Function1,Arity1,Location1}, . . . {ModN,FunctionN,ArityN,LocationN}] In this commit, the fourth element will just be an empty list, and we will change all code that look at or manipulate stacktraces. | |||
2011-05-16 | Write locks now check majority when needed. | Ulf Wiger | |
Since the table loader also sets (table) write locks, a special lock type, 'load', was needed. Unfortunately, this affects mnesia activity callbacks that redefine the lock operation. | |||
2011-03-02 | Remove wrong spec | Dan Gudmundsson | |
2011-03-02 | Mnesia dialyzer fixes | Dan Gudmundsson | |
With help from Kostis | |||
2010-06-04 | Merge branch 'uw/mnesia-overload' into dev | Erlang/OTP | |
* uw/mnesia-overload: Enable continuous monitoring of mnesia overload status | |||
2010-05-09 | Enable continuous monitoring of mnesia overload status | Ulf Wiger | |
Mnesia currently issues an event whenever it detects an overload condition. It recognizes two different types of overload: - whenever the message queue of mnesia_tm process grows large - when a log dump interval triggers before the previous dump is done These events could be used to trigger a load regulation mechanism to reduce the load until the condition seizes. The missing piece is that there is no facility to ask mnesia whether the overload condition still exists. This patch implements a couple of functions in mnesia_lib that can be used to sample the overload status. It has been tested in a load regulator component being developed by Erlang Solutions. No mnesia test suites have been run, since they are not available. No documentation has been updated. The functions in mnesia_lib are at any rate undocumented (as are all other functions in that module). A decision would have to be made about whether to provide a documented API on top of these functions. The internal state record of mnesia_recover has been modified. For this reason, a code change hook has been provided. | |||
2009-11-20 | The R13B03 release.OTP_R13B03 | Erlang/OTP | |