fault-tolerance

Erlang simple_one_for_one supervisor does not restart child

有些话、适合烂在心里 提交于 2020-06-18 12:35:13
问题 I have a test module and a simple_one_for_one supervisor. test.erl -module(test). -export([ run/1, do_job/1 ]). run(Fun) -> test_sup:start_child([Fun]). do_job(Fun) -> Pid = spawn(Fun), io:format("started ~p~n", [Pid]), {ok, Pid}. test_sup.erl -module(test_sup). -behaviour(supervisor). -export([start_link/0]). -export([init/1]). -export([start_child/1]). start_link() -> supervisor:start_link({local, ?MODULE}, ?MODULE, []). init(_Args) -> SupFlags = #{strategy => simple_one_for_one, intensity

Compiling an application for use in highly radioactive environments

二次信任 提交于 2020-01-09 05:43:05
问题 We are compiling an embedded C/C++ application that is deployed in a shielded device in an environment bombarded with ionizing radiation. We are using GCC and cross-compiling for ARM. When deployed, our application generates some erroneous data and crashes more often than we would like. The hardware is designed for this environment, and our application has run on this platform for several years. Are there changes we can make to our code, or compile-time improvements that can be made to

How to implement fault tolerance of REST server in client side?

ぃ、小莉子 提交于 2020-01-05 19:06:45
问题 I am working on a system that have a RESTful web service that can manipulate it (the service allows all CURD operations), and a web client that displays the system's data(most of the client was written in jQuery). In the standard operation scenario there are a main server and at least one backup server of my system and so at least two RESTful web service. So my question is in the case that my main server crashes, how can I make a client that was looking at the main server to now be looking at

How to implement fault tolerance of REST server in client side?

那年仲夏 提交于 2020-01-05 19:04:08
问题 I am working on a system that have a RESTful web service that can manipulate it (the service allows all CURD operations), and a web client that displays the system's data(most of the client was written in jQuery). In the standard operation scenario there are a main server and at least one backup server of my system and so at least two RESTful web service. So my question is in the case that my main server crashes, how can I make a client that was looking at the main server to now be looking at

Use case for Akka PoisonPill

孤街醉人 提交于 2019-12-25 15:50:20
问题 According to the Akka docs for PoisonPill : You can also send an actor the akka.actor.PoisonPill message, which will stop the actor when the message is processed. PoisonPill is enqueued as ordinary messages and will be handled after messages that were already queued in the mailbox. Although the usefulness/utility of such a feature may be obvious to an Akka Guru, to a newcomer, this sounds completely useless/reckless/dangerous. So I ask: What's the point of this message and when would one ever

Fault tolerant MPI implementations: status

冷暖自知 提交于 2019-12-24 02:42:18
问题 Which MPI implementations currently have support for fault tolerance, and what is the state of their development? 回答1: This question is probably too broad to give you a good answer here, especially since the answer will change as time progresses. In general, there's lots of fault tolerant work going on with various MPI implementations that is in various states of support. FT-MPI is an old project that isn't really in development anymore, but somewhat started it all in terms of integrated FT

NoSQL- Is it suitable for storing images?

只谈情不闲聊 提交于 2019-12-13 02:33:12
问题 I would like to store millions of images using a distributed fault tolerant system. While storing images in relational database has never been recommended, I was wondering if it is a suitable approach to store and manage image files in NoSQL databases. I would appreciate if you could share your experience in details here. (i.e. what NoSQL database did you use? it's advantages and disadvantages in this case, etc) Thanks 回答1: MongoDB has an API called GridFS which was made for storing binary

Kafka Streams stateStores fault tolerance exactly once?

南笙酒味 提交于 2019-12-13 01:43:50
问题 We're trying to achieve a deduplication service using Kafka Streams. The big picture is that it will use its rocksDB state store in order to check existing keys during process. Please correct me if I'm wrong, but to make those stateStores fault tolerant too, Kafka streams API will transparently copy the values in the stateStore inside a Kafka topic ( called the change Log). That way, if our service falls, another service will be able to rebuild its stateStore according to the changeLog found

Achieve Fault Tolerance with Consul Cluster

坚强是说给别人听的谎言 提交于 2019-12-12 15:17:15
问题 I have created consul server cluster using different ports in localhost. I used below commands for that. server 1: consul agent -server -bootstrap-expect=3 -data-dir=consul-data -ui -bind=127.0.0.1 -dns-port=8601 -http-port=8501 -serf-lan-port=8303 -serf-wan-port=8304 -server-port=8305 -node=node1 server 2: consul agent -server -bootstrap-expect=3 -data-dir=consul-data2 -ui -bind=127.0.0.1 -dns-port=8602 -http-port=8502 -serf-lan-port=8306 -serf-wan-port=8307 -server-port=8308 -node=node2