73 lines
6 KiB
Markdown
73 lines
6 KiB
Markdown
|
# Multiprocess Moneyrocket
|
||
|
|
|
||
|
|
On unix systems, the `--enable-multiprocess` build option can be passed to `./configure` to build new `moneyrocket-node`, `moneyrocket-wallet`, and `moneyrocket-gui` executables alongside existing `moneyrocketd` and `moneyrocket-qt` executables.
|
||
|
|
|
||
|
|
`moneyrocket-node` is a drop-in replacement for `moneyrocketd`, and `moneyrocket-gui` is a drop-in replacement for `moneyrocket-qt`, and there are no differences in use or external behavior between the new and old executables. But internally (after [#10102](https://github.com/moneyrocket/moneyrocket/pull/10102)), `moneyrocket-gui` will spawn a `moneyrocket-node` process to run P2P and RPC code, communicating with it across a socket pair, and `moneyrocket-node` will spawn `moneyrocket-wallet` to run wallet code, also communicating over a socket pair. This will let node, wallet, and GUI code run in separate address spaces for better isolation, and allow future improvements like being able to start and stop components independently on different machines and environments.
|
||
|
|
|
||
|
|
## Next steps
|
||
|
|
|
||
|
|
Specific next steps after [#10102](https://github.com/moneyrocket/moneyrocket/pull/10102) will be:
|
||
|
|
|
||
|
|
- [ ] Adding `-ipcbind` and `-ipcconnect` options to `moneyrocket-node`, `moneyrocket-wallet`, and `moneyrocket-gui` executables so they can listen and connect to TCP ports and unix socket paths. This will allow separate processes to be started and stopped any time and connect to each other.
|
||
|
|
- [ ] Adding `-server` and `-rpcbind` options to the `moneyrocket-wallet` executable so wallet processes can handle RPC requests directly without going through the node.
|
||
|
|
- [ ] Supporting windows, not just unix systems. The existing socket code is already cross-platform, so the only windows-specific code that needs to be written is code spawning a process and passing a socket descriptor. This can be implemented with `CreateProcess` and `WSADuplicateSocket`. Example: https://memset.wordpress.com/2010/10/13/win32-api-passing-socket-with-ipc-method/.
|
||
|
|
- [ ] Adding sandbox features, restricting subprocess access to resources and data. See [https://eklitzke.org/multiprocess-moneyrocket](https://eklitzke.org/multiprocess-moneyrocket).
|
||
|
|
|
||
|
|
## Debugging
|
||
|
|
|
||
|
|
The `-debug=ipc` command line option can be used to see requests and responses between processes.
|
||
|
|
|
||
|
|
## Installation
|
||
|
|
|
||
|
|
The multiprocess feature requires [Cap'n Proto](https://capnproto.org/) and [libmultiprocess](https://github.com/chaincodelabs/libmultiprocess) as dependencies. A simple way to get starting using it without installing these dependencies manually is to use the [depends system](../depends) with the `MULTIPROCESS=1` [dependency option](../depends#dependency-options) passed to make:
|
||
|
|
|
||
|
|
```
|
||
|
|
cd <MONEYROCKET_SOURCE_DIRECTORY>
|
||
|
|
make -C depends NO_QT=1 MULTIPROCESS=1
|
||
|
|
CONFIG_SITE=$PWD/depends/x86_64-pc-linux-gnu/share/config.site ./configure
|
||
|
|
make
|
||
|
|
src/moneyrocket-node -regtest -printtoconsole -debug=ipc
|
||
|
|
MONEYROCKETD=moneyrocket-node test/functional/test_runner.py
|
||
|
|
```
|
||
|
|
|
||
|
|
The configure script will pick up settings and library locations from the depends directory, so there is no need to pass `--enable-multiprocess` as a separate flag when using the depends system (it's controlled by the `MULTIPROCESS=1` option).
|
||
|
|
|
||
|
|
Alternately, you can install [Cap'n Proto](https://capnproto.org/) and [libmultiprocess](https://github.com/chaincodelabs/libmultiprocess) packages on your system, and just run `./configure --enable-multiprocess` without using the depends system. The configure script will be able to locate the installed packages via [pkg-config](https://www.freedesktop.org/wiki/Software/pkg-config/). See [Installation](https://github.com/chaincodelabs/libmultiprocess#installation) section of the libmultiprocess readme for install steps. See [build-unix.md](build-unix.md) and [build-osx.md](build-osx.md) for information about installing dependencies in general.
|
||
|
|
|
||
|
|
## IPC implementation details
|
||
|
|
|
||
|
|
Cross process Node, Wallet, and Chain interfaces are defined in
|
||
|
|
[`src/interfaces/`](../src/interfaces/). These are C++ classes which follow
|
||
|
|
[conventions](developer-notes.md#internal-interface-guidelines), like passing
|
||
|
|
serializable arguments so they can be called from different processes, and
|
||
|
|
making methods pure virtual so they can have proxy implementations that forward
|
||
|
|
calls between processes.
|
||
|
|
|
||
|
|
When Wallet, Node, and Chain code is running in the same process, calling any
|
||
|
|
interface method invokes the implementation directly. When code is running in
|
||
|
|
different processes, calling an interface method invokes a proxy interface
|
||
|
|
implementation that communicates with a remote process and invokes the real
|
||
|
|
implementation in the remote process. The
|
||
|
|
[libmultiprocess](https://github.com/chaincodelabs/libmultiprocess) code
|
||
|
|
generation tool internally generates proxy client classes and proxy server
|
||
|
|
classes for this purpose that are thin wrappers around Cap'n Proto
|
||
|
|
[client](https://capnproto.org/cxxrpc.html#clients) and
|
||
|
|
[server](https://capnproto.org/cxxrpc.html#servers) classes, which handle the
|
||
|
|
actual serialization and socket communication.
|
||
|
|
|
||
|
|
As much as possible, calls between processes are meant to work the same as
|
||
|
|
calls within a single process without adding limitations or requiring extra
|
||
|
|
implementation effort. Processes communicate with each other by calling regular
|
||
|
|
[C++ interface methods](../src/interfaces/README.md). Method arguments and
|
||
|
|
return values are automatically serialized and sent between processes. Object
|
||
|
|
references and `std::function` arguments are automatically tracked and mapped
|
||
|
|
to allow invoked code to call back into invoking code at any time, and there is
|
||
|
|
a 1:1 threading model where any thread invoking a method in another process has
|
||
|
|
a corresponding thread in the invoked process responsible for executing all
|
||
|
|
method calls from the source thread, without blocking I/O or holding up another
|
||
|
|
call, and using the same thread local variables, locks, and callbacks between
|
||
|
|
calls. The forwarding, tracking, and threading is implemented inside the
|
||
|
|
[libmultiprocess](https://github.com/chaincodelabs/libmultiprocess) library
|
||
|
|
which has the design goal of making calls between processes look like calls in
|
||
|
|
the same process to the extent possible.
|