Manu Zhang created GEARPUMP-66:
----------------------------------
Summary: Investigate on Akka-persistence as a general storage
implementation
Key: GEARPUMP-66
URL: https://issues.apache.org/jira/browse/GEARPUMP-66
Project: Apache Gearpump
Issue Type: New Feature
Reporter: Manu Zhang
imported from [https://github.com/gearpump/gearpump/issues/1822] on behalf of
[~clockfly],
Motive:
Currently we use replicated memory to store some data, it has risks when the
whole cluster is brought down due to power failure.
We need to investigate wether Akka-persistence can be used as a distributed,
pluggable, general storage to persist data like:
# application timestamp
# application submission info (like jar, and confgs...)
# application runtime storage for KV.
What is the expected output for this investigation:
We expect to see a test project in scala which use "akka persistence", it
should:
# provide a API to read/write large chunk of data in a streaming way, suggest
to test it on Tested on HDFS, and Redis.
# connect with akka-data-replication to persist the CRDT data, and why this can
still be consistent?
# Demo how this can be plugged, how to switch between HDFS and Redis. What is
the new classpath introduced for each storage(HDFS or Redis)?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
