| commit | cc7d2f0ce46f2dd628a548b819d4e9a1f8ff99a9 | [log] [tgz] |
|---|---|---|
| author | Murtadha Hubail <mhubail@apache.org> | Wed Dec 13 23:11:09 2017 +0300 |
| committer | Murtadha Hubail <mhubail@apache.org> | Wed Dec 13 20:30:36 2017 -0800 |
| tree | 96a25c3398009bb119acb6413a2a81574f9eb0fe | |
| parent | 54249a8a9fbb2561bcb9cdc9c9f1e4470df11d80 [diff] |
[ASTERIXDB-2198][REPL] Introduce Dynamic Replica Placement
- user model changes: no
- storage format changes: no
- interface changes: yes
- Add IReplicationMessage and IReplicaTask.
- Add notifyMetadataNodeChange to IFaultToleranceStrategy.
- Add register to IReplicationManager to allow registering
replicas at runtime.
Details:
- Add cluster APIs for:
- changing partition master node.
- changing metadata node.
- Add NC storage management API for promoting a partition replica
to master replica.
- Implement changing metadata node at runtime in
MetadataNodeFaultToleranceStrategy.
- Allow MetadataNodeFaultToleranceStrategy to have zero replica
at initialization.
- Add a flag to LangExecutionUtil to skip storage distribution
check at the end of each test.
- Add test case for metadata node failover as follows:
1- start with nc1 as metadata node.
2- add replica for metadata partition on nc2 at runtime.
3- performs metadata transactions on nc1.
4- promote metadata partition on nc2.
5- failover metadata node to nc2.
6- ensure the effects of the metadata transactions on (2) exists.
7- performs more metadata transactions on nc2.
8- ensure the effects of the metadata transactions on (7) exists.
Change-Id: I11f82efcad29d2c37324fe9d3c11d872b0348f49
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2215
Sonar-Qube: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Contrib: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Reviewed-by: Till Westmann <tillw@apache.org>
AsterixDB is a BDMS (Big Data Management System) with a rich feature set that sets it apart from other Big Data platforms. Its feature set makes it well-suited to modern needs such as web data warehousing and social data storage and analysis. AsterixDB has:
Data model
A semistructured NoSQL style data model (ADM) resulting from extending JSON with object database ideas
Query languages
Two expressive and declarative query languages (SQL++ and AQL) that support a broad range of queries and analysis over semistructured data
Scalability
A parallel runtime query execution engine, Apache Hyracks, that has been scale-tested on up to 1000+ cores and 500+ disks
Native storage
Partitioned LSM-based data storage and indexing to support efficient ingestion and management of semistructured data
External storage
Support for query access to externally stored data (e.g., data in HDFS) as well as to data stored natively by AsterixDB
Data types
A rich set of primitive data types, including spatial and temporal data in addition to integer, floating point, and textual data
Indexing
Secondary indexing options that include B+ trees, R trees, and inverted keyword (exact and fuzzy) index types
Transactions
Basic transactional (concurrency and recovery) capabilities akin to those of a NoSQL store
Learn more about AsterixDB at its website.
To build AsterixDB from source, you should have a platform with the following:
Instructions for building the master:
Checkout AsterixDB master:
$git clone https://github.com/apache/asterixdb.git
Build AsterixDB master:
$cd asterixdb $mvn clean package -DskipTests
Here are steps to get AsterixDB running on your local machine:
Start a single-machine AsterixDB instance:
$cd asterixdb/asterix-server/target/asterix-server-*-binary-assembly/ $./opt/local/bin/start-sample-cluster.sh
Good to go and run queries in your browser at:
http://localhost:19001
Read more documentations to learn the data model, query language, and how to create a cluster instance.