[erlang-questions] Process migration/ Process state extraction/ injection

Philippe McLean <>
Tue Jul 31 22:34:54 CEST 2012


What goals are you trying to achieve? many problems can be solved with
another level of indirection, but a robust approach to error handling and
process creation might give the same or better results.

On Tue, Jul 31, 2012 at 11:21 AM, Tyron Zerafa <>wrote:

> Hey again,
>     I am thinking that a weaker form of such mobility might suffice for my
> project, but I am not sure. In this weaker form, it is enough to transfer
> the code and execution can restart again. I need this primary to implement
> the code-on-demand and remote-evaluation architectures. I do not believe
> that this is so complex in Erlang, in fact if I remember correctly some
> functionality already exists for such.
>
>
> On Tue, Jul 31, 2012 at 8:15 PM, Gleb Peregud <> wrote:
>
>> On Tue, Jul 31, 2012 at 8:11 PM, Tyron Zerafa <>
>> wrote:
>> > Hey,
>> >     My primary intention is to implement strong mobility of processes.
>> Let's
>> > say that process A is running on Node 1, I want to be able to suspend
>> this
>> > process, transfer it to Node 2 and resume such process from where it
>> halted.
>> > I believe that in order to achieve such I need to somehow preserve the
>> stack
>> > trace, memory and other info.
>>
>> This task is non-trivial and will require a lot of work with ERTS and
>> whole Erlang VM. Things you have to handle are:
>> - stack
>> - heap
>> - binary refs
>> - monitors
>> - links
>> - ets ownership
>> - port ownership
>> - messages sent to old process pid?
>> - replacing old pid with new in other processes?
>> - replacing old process with "replay" process?
>>
>> And I'm sure that those are not all details which will have to be handled.
>>
>> Cheers,
>> Gleb
>>
>
>
>
> --
> Best Regards,
> Tyron Zerafa
>
>
> _______________________________________________
> erlang-questions mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-questions
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20120731/12204f44/attachment.html>


More information about the erlang-questions mailing list