- 浏览: 28495 次
- 性别:
- 来自: 广州
最新评论
读erlang编程指南Mnesia笔记:
1.mnesia 是ets和dets上面封装一层的事务层。底层实现用的是这,重点加强了锁和分布式的适应。
2.不应使用mnesia的场合:
2.1 简单的键-值查询;--------最好用ets或dict
巨大的二进制数据:图片,音频;--------把每个记录和文件脱离,只记录文件名之类。(好像还有个开源数据库可用的?)2.2 一个持续的日志;----------disk_log库
2.3 一个必须存储GB级别的数据库;--------这个不是首选,但是可以用来[/color]缓存用户会话(在线)数据,定时写入到指定数据库中。
2.4 一直增长的大型数据档案。
3.Mnesia封装成一个OTP的[color=red]应用程序,要创建一个空模式并存在磁盘或内存上以启动它,有了模式才会有表。
create_schema(DiscNodes) -> ok | {error,Reason}
application:start(mnesia).-----------在应用时要先启动,也可用mnesia:start().
create_table(Name, TabDef) -> {atomic, ok} | {aborted, Reason
4.小技巧:要知道一个节点ping通么:net_adm:pin(Nodes).->pong |pang
node()返回本节点名,nodes()返回所有其它节点名。
5.一个项目中有多个应用程序,这些应用程序是平行的,如果这里有时序问题(即要求加载完某些表再运行这个应用程序时,要在些进程中使用(特别是大量数据要加载时)
wait_for_tables(TabList,Timeout) -> ok | {timeout, BadTabList} | {error, Reason}
Some applications need to wait for certain tables to be accessible in order to do useful work. mnesia:wait_for_tables/2 hangs until all tables in the TabList are accessible, or until timeout is reached.
如果是{timeout,Tablelist}----->则忽略,假定他们已加载吧。
6.事务处理:
transaction(Fun [[, Args], Retries]) -> {aborted, Reason} | {atomic, ResultOfFun}
This function executes the functional object Fun with arguments Args as a transaction.
The code which executes inside the transaction can consist of a series of table manipulation functions. If something goes wrong inside the transaction as a result of a user error or a certain table not being available, the entire transaction is aborted and the function transaction/1 returns the tuple {aborted, Reason}.
If all is well, {atomic, ResultOfFun} is returned where ResultOfFun is the value of the last expression in Fun.
A function which adds a family to the database can be written as follows if we have a structure {family, Father, Mother, ChildrenList}:
This code adds a set of people to the database. Running this code within one transaction will ensure that either the whole family is added to the database, or the whole transaction aborts. For example, if the last child is badly formatted, or the executing process terminates due to an 'EXIT' signal while executing the family code, the transaction aborts. Accordingly, the situation where half a family is added can never occur.
It is also useful to update the database within a transaction if several processes concurrently update the same records. For example, the function raise(Name, Amount), which adds Amount to the salary field of a person, should be implemented as follows:
以自己主动调用abort/2来终止事务的情况:
When this function executes within a transaction, several processes running on different nodes can concurrently execute the raise/2 function without interfering with each other.
死锁会终止后重试:
Since Mnesia detects deadlocks, a transaction can be restarted any number of times. This function will attempt a restart as specified in Retries. Retries must be an integer greater than 0 or the atom infinity. Default is infinity.
防止边界操作:
即不在要在事务里面执行无法撤消的操作(如发消息,io:format/2).
7.数据的读写,删,备份?to_do
8.数据的脏(dirty)读写,删,更新
这个drity比事务中平均快10倍哦。为了保证数据的一致性:
对于不是分布式的:只在单一的进程去序列化所有的破坏性操作(写,更新)其它进程只是查询类(如果要改变,发消息到这个进程来做,给个接口给外部)
对于分布式:如果还是采用上面的方法用一个节点去序列化,则会负载过大,所以要会开,如偶数键的在一个节点上,奇数键的在另一个节点上来平分压力;
另外还有执行破坏操作时网络断了怎么办?数据就不一致了:
这个在脏操作中是无法避免的,那么事务操作时会发生这种情况么?
会,假定两个节点在副本上各自更新时,网络故障,二个表不一致则:用
set_master_nodes(Tab, MasterNodes[/color)] -> ok | {error, Reason}来设置主节点,如果网络分区,那么mnesia会自动把主节点上的内容同步复制下去并复制回来,所有分节点不在主节点上更新的都会被丢弃。所以考虑主节点的重要性!!!!
9.表的遍历:
first/1 ----next/2
select
match
foldl
10.在工业系统级别的应用中,还有[color=red]表分段,备份,故障恢复,Mnesia事件和无盘节点。还在去看去找!!!!!to_do.
11.erlang doc里面的内容:
Mnesia is A Distributed Telecommunications DBMS 强于分布式。
Mnesia privide:
1. A relational/object hybrid data model which is suitable for telecommunications applications.----可兼容多种适合电信业务的数据类型。
2. A specifically designed DBMS query language, QLC (as an add-on library).
3. Persistence. Tables may be coherently kept on disc as well as in main memory.可存于磁盘,内存,或两者都有的。
4.Replication. Tables may be replicated at several nodes.几个节点共享,为分布式而生的。
5.Atomic transactions. A series of table manipulation operations can be grouped into a single atomic transaction.事务处理
6.Location transparency. Programs can be written without knowledge of the actual location of data.
7.Extremely fast real time data searches.快
8.Schema manipulation routines. It is possible to reconfigure the DBMS at runtime without stopping the system. 热更新,不用停机。
These copies can be dumped to disc at regular intervals. However, updates to these copies are not written to disc on a transaction basis.所有的数据在内存中有一定间隔的入到磁盘中(可设置时间),便是更新这些不是在事务中的。
mnesia:add_table_index(person, age)
可以给一个table加多个index相当于key,不过会使空间变大且插入变慢。
Note:It is more than 10 times more efficient to read records dirty than within a transaction.
Note: currently 'ordered_set' is not supported for 'disc_only_copies'.
delete/3 delete_object/3的区别:If a table is of type bag, we may sometimes want to delete only some of the records with a certain key. This can be done with the delete_object/3 function. A complete record must be supplied to this function.
http://shiningray.cn/docs/mnesia-a-distributed-robust-dbms-for-telecommunications-applications
1.mnesia 是ets和dets上面封装一层的事务层。底层实现用的是这,重点加强了锁和分布式的适应。
2.不应使用mnesia的场合:
2.1 简单的键-值查询;--------最好用ets或dict
巨大的二进制数据:图片,音频;--------把每个记录和文件脱离,只记录文件名之类。(好像还有个开源数据库可用的?)2.2 一个持续的日志;----------disk_log库
2.3 一个必须存储GB级别的数据库;--------这个不是首选,但是可以用来[/color]缓存用户会话(在线)数据,定时写入到指定数据库中。
2.4 一直增长的大型数据档案。
3.Mnesia封装成一个OTP的[color=red]应用程序,要创建一个空模式并存在磁盘或内存上以启动它,有了模式才会有表。
create_schema(DiscNodes) -> ok | {error,Reason}
application:start(mnesia).-----------在应用时要先启动,也可用mnesia:start().
create_table(Name, TabDef) -> {atomic, ok} | {aborted, Reason
4.小技巧:要知道一个节点ping通么:net_adm:pin(Nodes).->pong |pang
node()返回本节点名,nodes()返回所有其它节点名。
5.一个项目中有多个应用程序,这些应用程序是平行的,如果这里有时序问题(即要求加载完某些表再运行这个应用程序时,要在些进程中使用(特别是大量数据要加载时)
wait_for_tables(TabList,Timeout) -> ok | {timeout, BadTabList} | {error, Reason}
Some applications need to wait for certain tables to be accessible in order to do useful work. mnesia:wait_for_tables/2 hangs until all tables in the TabList are accessible, or until timeout is reached.
如果是{timeout,Tablelist}----->则忽略,假定他们已加载吧。
6.事务处理:
transaction(Fun [[, Args], Retries]) -> {aborted, Reason} | {atomic, ResultOfFun}
This function executes the functional object Fun with arguments Args as a transaction.
The code which executes inside the transaction can consist of a series of table manipulation functions. If something goes wrong inside the transaction as a result of a user error or a certain table not being available, the entire transaction is aborted and the function transaction/1 returns the tuple {aborted, Reason}.
If all is well, {atomic, ResultOfFun} is returned where ResultOfFun is the value of the last expression in Fun.
A function which adds a family to the database can be written as follows if we have a structure {family, Father, Mother, ChildrenList}:
add_family({family, F, M, Children}) -> ChildOids = lists:map(fun oid/1, Children), Trans = fun() -> mnesia:write(F#person{children = ChildOids}, mnesia:write(M#person{children = ChildOids}, Write = fun(Child) -> mnesia:write(Child) end, lists:foreach(Write, Children) end, mnesia:transaction(Trans). oid(Rec) -> {element(1, Rec), element(2, Rec)}.
This code adds a set of people to the database. Running this code within one transaction will ensure that either the whole family is added to the database, or the whole transaction aborts. For example, if the last child is badly formatted, or the executing process terminates due to an 'EXIT' signal while executing the family code, the transaction aborts. Accordingly, the situation where half a family is added can never occur.
It is also useful to update the database within a transaction if several processes concurrently update the same records. For example, the function raise(Name, Amount), which adds Amount to the salary field of a person, should be implemented as follows:
以自己主动调用abort/2来终止事务的情况:
raise(Name, Amount) -> mnesia:transaction(fun() -> case mnesia:wread({person, Name}) of [P] -> Salary = Amount + P#person.salary, P2 = P#person{salary = Salary}, mnesia:write(P2); _ -> mnesia:abort("No such person") end end).
When this function executes within a transaction, several processes running on different nodes can concurrently execute the raise/2 function without interfering with each other.
死锁会终止后重试:
Since Mnesia detects deadlocks, a transaction can be restarted any number of times. This function will attempt a restart as specified in Retries. Retries must be an integer greater than 0 or the atom infinity. Default is infinity.
防止边界操作:
即不在要在事务里面执行无法撤消的操作(如发消息,io:format/2).
7.数据的读写,删,备份?to_do
8.数据的脏(dirty)读写,删,更新
这个drity比事务中平均快10倍哦。为了保证数据的一致性:
对于不是分布式的:只在单一的进程去序列化所有的破坏性操作(写,更新)其它进程只是查询类(如果要改变,发消息到这个进程来做,给个接口给外部)
对于分布式:如果还是采用上面的方法用一个节点去序列化,则会负载过大,所以要会开,如偶数键的在一个节点上,奇数键的在另一个节点上来平分压力;
另外还有执行破坏操作时网络断了怎么办?数据就不一致了:
这个在脏操作中是无法避免的,那么事务操作时会发生这种情况么?
会,假定两个节点在副本上各自更新时,网络故障,二个表不一致则:用
set_master_nodes(Tab, MasterNodes[/color)] -> ok | {error, Reason}来设置主节点,如果网络分区,那么mnesia会自动把主节点上的内容同步复制下去并复制回来,所有分节点不在主节点上更新的都会被丢弃。所以考虑主节点的重要性!!!!
9.表的遍历:
first/1 ----next/2
select
match
foldl
10.在工业系统级别的应用中,还有[color=red]表分段,备份,故障恢复,Mnesia事件和无盘节点。还在去看去找!!!!!to_do.
11.erlang doc里面的内容:
Mnesia is A Distributed Telecommunications DBMS 强于分布式。
Mnesia privide:
1. A relational/object hybrid data model which is suitable for telecommunications applications.----可兼容多种适合电信业务的数据类型。
2. A specifically designed DBMS query language, QLC (as an add-on library).
3. Persistence. Tables may be coherently kept on disc as well as in main memory.可存于磁盘,内存,或两者都有的。
4.Replication. Tables may be replicated at several nodes.几个节点共享,为分布式而生的。
5.Atomic transactions. A series of table manipulation operations can be grouped into a single atomic transaction.事务处理
6.Location transparency. Programs can be written without knowledge of the actual location of data.
7.Extremely fast real time data searches.快
8.Schema manipulation routines. It is possible to reconfigure the DBMS at runtime without stopping the system. 热更新,不用停机。
These copies can be dumped to disc at regular intervals. However, updates to these copies are not written to disc on a transaction basis.所有的数据在内存中有一定间隔的入到磁盘中(可设置时间),便是更新这些不是在事务中的。
mnesia:add_table_index(person, age)
可以给一个table加多个index相当于key,不过会使空间变大且插入变慢。
Note:It is more than 10 times more efficient to read records dirty than within a transaction.
Note: currently 'ordered_set' is not supported for 'disc_only_copies'.
delete/3 delete_object/3的区别:If a table is of type bag, we may sometimes want to delete only some of the records with a certain key. This can be done with the delete_object/3 function. A complete record must be supplied to this function.
http://shiningray.cn/docs/mnesia-a-distributed-robust-dbms-for-telecommunications-applications
发表评论
-
Erlang 简单的节点互连
2014-03-19 23:41 552自己写的游戏跨服初步构架,以后再一点点完善,先记下时间线哈。 ... -
简单erlang节点互连实验
2014-03-10 15:53 761如果erlang:节点test1,test2互连接: 1.节点 ... -
Erlang OTP gen_event (1)
2014-02-26 15:06 1063演示gen_event的运行过程: mod_event_ma ... -
Erlang OTP gen_event (0)
2014-02-26 14:30 1191原英文文档:http://www.erlang.org/erl ... -
erlang efficient guide 3
2013-08-19 22:19 1111* 3 Common Caveats * 3常见 ... -
erlang efficient guide 2
2013-08-18 01:02 8622 The Eight Myths of Erlang Per ... -
fun还是如以前一样狂跩吊么?
2013-08-16 22:26 611fun这么好用。为什么老大在最近都说不要用? gen:cal ... -
emacs 的erlang-flymake
2013-08-14 15:15 1462emacs 设置erlang-flymake erlang- ... -
erlang ets
2013-07-22 23:08 1857参见:http://www.cnblogs.com ... -
erlang的编程规范
2013-03-26 17:17 1945Programming Rules and Conventio ... -
进程环
2013-03-18 16:48 817编写一个程序,它生成N ... -
匿名函数fun
2012-12-15 16:12 812lists:map(fun/1,[1,2,3]). 小试匿名函 ... -
并发编程实战otp--open telecom platform 二
2012-10-10 23:17 1148第二章:Erlang语言精要。 shell 的启动参数h ... -
并发编程实战otp--open telecom platform 一
2012-10-10 23:16 12131.erlang 的进程模型: 并发的基本单位是进程, ... -
learn some erlang
2012-10-09 22:54 717Erlang has this very pragm ... -
erlang语句块的简洁使用
2012-09-25 22:48 677begin end语句块的简洁使用:问题描述:将一堆人 ... -
命令式编程语言的标杆
2012-09-25 09:47 685命令式编程语言的标杆: 1.进程必须是语言的核心; 2.任何进 ... -
emacs与erlang的完美结合
2012-09-23 22:48 12861.在emacs中使用c+x c+z 启动erlang she ...
相关推荐
Erlang是一种高级编程语言,特别为构建分布式、并发、实时和容错系统而设计。在标题中的"erlang-18.3-1.el7.centos.x86_64.zip",我们看到的是Erlang的一个特定版本,18.3,针对64位的CentOS 7操作系统(el7)的...
4. **OTP(Open Telecom Platform)框架**:OTP提供了一组标准库和设计模式,用于构建可靠的、可维护的系统,包括Mnesia数据库、Supervisor进程监控和GenServer行为模式等。 5. **函数式编程**:Erlang采用函数式...
erlang-mnesia-19.3.6.4-1.el7.x86_64.rpm
RabbitMQ安装需要的安装包
### Erlang Mnesia:分布式数据库管理系统 #### 一、引言与概述 Mnesia是一款由爱立信(Ericsson)开发并维护的分布式数据库管理系统(DBMS),它被设计用于支持电信应用以及其他需要持续运行和具备软实时特性的...
4. **Mnesia数据库**:Mnesia是OTP的一部分,是一个分布式事务型数据库,适用于实时系统。手册会详细阐述如何创建、读取、更新和删除数据,以及如何进行事务操作和数据分发。 5. **行为模式(Behaviours)**:如`...
- **OTP(开放电信平台)**:Erlang OTP是一套库和设计原则,提供了构建可靠系统的框架,包括Mnesia数据库、Event Manager、Supervisor和GenServer等行为模块。 学习Erlang时,你需要掌握以下核心概念: - **BEAM...
Mnesia是Erlang内置的分布式数据库,适用于实时、分布式和高可用性应用。在游戏服务器中,它可以用来存储玩家数据、游戏状态等信息,支持快速读写和容错。 ### 7. WebSockets集成 游戏服务器常常需要与客户端建立长...
* 数据库层:使用Erlang的ETS、Mnesia、MySQL、MongoDB等数据库来存储游戏数据。 游戏服务器实现 在实现游戏服务器时,我们需要考虑以下几个方面: * 玩家和NPC的进程模型:使用Erlang的轻量级进程来模拟玩家和...
1.2.Mnesia.数据库管理系统(DBMS 2、开始.Mnesia 2.1.首次启动.Mnesia 2.2.一个示例 3、构建.Mnesia.数据库 3.1.定义模式 3.2.数据模型 3.3.启动.Mnesia 3.4.创建新表 4、事务和其他上下文存取 ...
《Mnesia用户手册》是专为理解和操作Erlang编程语言中的Mnesia数据库管理系统而编写的详尽指南。Mnesia是Erlang OTP (Open Telephony Platform) 库中的一个核心组件,它是一个强大的分布式数据库系统,特别适用于...
Mnesia是一个分布式数据库管理系统,适合于电信和其它需要持续运行和具备软实时特性的Erlang应用,越来越受关注和使用,但是目前Mnesia资料却不多,很多都只有官方的用户指南。下面的内容将着重说明 如何做 Mnesia ...
Examples are included how to start an Erlang session, specify a Mnesia database directory, initialize a database schema, start Mnesia, and create tables. Initial prototyping of record definitions is ...
**ecto_mnesia:Ecto适配器与Mnesia Erlang术语数据库** ecto_mnesia是Ecto框架的一个适配器,它允许开发者在Elixir应用中使用Mnesia,一个内置在Erlang虚拟机(VM)中的分布式、事务性的术语数据库。Mnesia以其高...
4. **库和工具的更新**:OTP中的各种库(如Mnesia数据库、ERTS(Erlang Run-Time System)和其他并发工具)可能进行了升级,以适应新的需求和改进功能。 5. **并发与分布式系统支持**:Erlang以其轻量级进程和消息...
在"amnesia-1.6.2"这个压缩包中,你可以找到AMNESIA库的源代码和其他相关资源。通过阅读源代码和文档,开发者可以深入了解其内部工作原理,定制自己的数据库解决方案,或者为项目贡献代码。对于想要在Erlang项目中...
### Mnesia数据库:Erlang中的分布式数据库管理系统 #### 引言 Mnesia,作为Erlang编程语言的一部分,是一款由爱立信公司开发的分布式数据库管理系统(DBMS)。自1997年以来,Mnesia一直是Open Telecom Platform...