IGinX is an open source polystore system. A polystore system provides an integrated data management service over a set of one or more potentially heterogeneous database/storage engines, serving heterogeneous workloads.
Currently, IGinX directly supports big data service over relational database PostgreSQL, time series databases InfluxDB/IoTDB/TimescaleDB/OpenTSDB, and Parquet data files.
Since ZooKeeper, IGinX and IoTDB are all developed using Java, Java needs to be installed first. If a running environment of JDK >= 1.8 has been installed locally, skip this step entirely.
First, visit the official Java website to download the JDK package for your current system.
Installation
$ cd ~/Downloads
$ tar -zxf jdk-8u181-linux-x64.gz # unzip files
$ mkdir /opt/jdk
$ mv jdk-1.8.0_181 /opt/jdk/
Edit the ~/.bashrc file and add the following two lines at the end of the file:
export JAVA_HOME = /usr/jdk/jdk-1.8.0_181
export PATH=$PATH:$JAVA_HOME/bin
Load the file with the changed configuration (into shell scripts):
$ source ~/.bashrc
$ java -version
java version "1.8.0_181"
Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
If the words above are displayed, it means the installation was successful.
Maven is a build automation tool used primarily to build and managa Java projects. If you need to compile from the source code, you also need to install a Maven environment >= 3.6. Otherwise, skip this step entirely.
$ wget http://mirrors.hust.edu.cn/apache/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.tar.gz
$ tar -xvf apache-maven-3.3.9-bin.tar.gz
$ sudo mv -f apache-maven-3.3.9 /usr/local/
Edit the ~/.bashrc file and add the following two lines at the end of the file:
export MAVEN_HOME=/usr/local/apache-maven-3.3.9
export PATH=${PATH}:${MAVEN_HOME}/bin
Load the file with the changed configuration (into shell scripts):
$ source ~/.bashrc
$ mvn -v
Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 2019-04-05T03:00:29+08:00)
If the words above are displayed, that means the installation was successful.
Docker provides an official installation script that allows users to automatically install it by entering the command:
$ curl -fsSL https://get.docker.com | bash -s docker --mirror Aliyun
You can also use the internal daocloud one-click installation command:
$ curl -sSL https://get.daocloud.io/docker | sh
Run this command to start the docker engine and check the docker version:
$ systemctl start docker
$ docker version
If the words above are displayed, it means the installation was successful:
Client: Docker Engine - Community
Version: 20.10.8
API version: 1.41
Go version: go1.16.6
Git commit: 3967b7d
Built: Fri Jul 30 19:55:49 2021
OS/Arch: linux/amd64
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.8
API version: 1.41 (minimum version 1.12)
Go version: go1.16.6
Git commit: 75249d8
Built: Fri Jul 30 19:54:13 2021
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.4.9
GitCommit: e25210fe30a0a703442421b0f60afac609f950a3
runc:
Version: 1.0.1
GitCommit: v1.0.1-0-g4144b63
docker-init:
Version: 0.19.0
GitCommit: de40ad0
Currently, the docker image of IGinX needs to be manually installed locally. First, you need to download the IGinX source code:
$ cd ~
$ git clone git@github.com:IGinX-THU/IGinX.git # Pull the latest IGinX code
$ cd IGinX
Then start building the IGinX image:
Currently, there are two types of IGinX image construction:
In this method, ZooKeeper, IoTDB and IGinX run as 3 separate containers with a custom network bridge which enables these three containers to communicate with each other.
Before building the image, the params in conf/config.properties need to be changed. The IP address for ZooKeeper and IoTDB should be changed to the hostnames of those containers. Otherwise, IGinX will not be able to access them.
# IoTDB:iotdb12 (param before the first #)
# ZooKeeper:zkServer
storageEngineList=iotdb12#6667#iotdb12#username=root#password=root#sessionPoolSize=20#has_data=false#is_read_only=false
zookeeperConnectionString=zkServer:2181
Hostnames for Zookeeper and IoTDB containers can be changed in $IGINX_HOME/docker/oneShot/docker-compose.yaml
services:
zookeeper:
hostname: "custom_zookeeper_hostname" #default: zkServer
iotdb:
hostname: "custom_IoTDB_hostname" #default: iotdb12
# conf/config.properties should be changed accordingly
Then use the following command to build image and run:
$ cd docker/oneShot
$ ./build_and_run_iginx_docker.sh
The following words are displayed to indicate that the image was built and run successfully:
[+] Building 729.6s (12/12) FINISHED
=> [iginx internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [iginx internal] load build definition from Dockerfile 0.0st
=> => transferring dockerfile: 384B 0.0s
=> [iginx internal] load metadata for docker.io/library/maven:3-amazoncorretto-8 5.5s2
=> [iginx internal] load metadata for docker.io/library/amazoncorretto:8 5.6s
=> CACHED [iginx stage-1 1/2] FROM docker.io/library/amazoncorretto:8@sha256:f9290c74c5587f1e651bd4f0b783f8342aba347d84 0.0s
=> [iginx internal] load build context 0.8s
=> => transferring context: 1.64MB 0.8s/
=> CACHED [iginx builder 1/4] FROM docker.io/library/maven:3-amazoncorretto-8@sha256:c9d6016fad9c479b874f270a80d80f8913 0.0s
=> [iginx builder 2/4] COPY . /root/IGinX 1.0s
=> [iginx builder 3/4] WORKDIR /root/IGinX 0.1s
=> [iginx builder 4/4] RUN --mount=type=cache,target=/root/.m2 mvn clean package -pl core,dataSources/iotdb12 -am -Dm 721.4s
=> [iginx stage-1 2/2] COPY --from=builder /root/IGinX/core/target/iginx-core-dev /root/IGinX 0.1s
=> [iginx] exporting to image 0.4s
=> => exporting layers 0.3s
=> => writing image sha256:3e83d7c3510bd41f9e0404bef932e1c7f48bed869dccac3ba070cbc2b29b966c 0.0s
=> => naming to docker.io/library/oneshot-iginx 0.0s
[+] Running 4/4
✔ Network oneshot_net Created 0.6s
✔ Container iotdb Started 1.6s
✔ Container zookeeper Started 1.6s
✔ Container iginx1 Started
After this step, 127.0.0.1:10001 will be accessable for IGinX service.
Warning: Before starting to build the IGinX image, you need to modify the network address parameters in IGinX. All “127.0.0.1” should be replaced by “host.docker.internal” to enable the IGinX container to communicate with ZooKeeper, database services that run on host machine.
Use the following command to build the IGinX image:
$ cd docker/onlyIginx
$ ./build_iginx_docker.sh
The following words are displayed to indicate that the image was built successfully:
[+] Building 887.9s (12/12) FINISHED
=> [internal] load build definition from Dockerfile-iginx 0.1s
=> => transferring dockerfile: 406B 0.0s
=> [internal] load .dockerignore 0.1s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for docker.io/library/openjdk:11-jre-slim 5.3s
=> [internal] load metadata for docker.io/library/maven:3-amazoncorretto-8 3.3s
=> [internal] load build context 3.6s
=> => transferring context: 475.61MB 3.5s
=> CACHED [builder 1/4] FROM docker.io/library/maven:3-amazoncorretto-8@sha256:c9d6016fad9c479b874f270a80d80f891 0.0s
=> [stage-1 1/2] FROM docker.io/library/openjdk:11-jre-slim@sha256:93af7df2308c5141a751c4830e6b6c5717db102b3b31 38.3s
=> => resolve docker.io/library/openjdk:11-jre-slim@sha256:93af7df2308c5141a751c4830e6b6c5717db102b3b31f012ea29d 0.1s
=> => sha256:764a04af3eff09cc6a29bcc19cf6315dbea455d7392c1a588a5deb331a929c29 7.55kB / 7.55kB 0.0s
=> => sha256:1efc276f4ff952c055dea726cfc96ec6a4fdb8b62d9eed816bd2b788f2860ad7 31.37MB / 31.37MB 25.6s
=> => sha256:a2f2f93da48276873890ac821b3c991d53a7e864791aaf82c39b7863c908b93b 1.58MB / 1.58MB 2.7s
=> => sha256:12cca292b13cb58fadde25af113ddc4ac3b0c5e39ab3f1290a6ba62ec8237afd 212B / 212B 1.2s
=> => sha256:93af7df2308c5141a751c4830e6b6c5717db102b3b31f012ea29d842dc4f2b02 549B / 549B 0.0s
=> => sha256:884c08d0f406a81ae1b5786932abaf399c335b997da7eea6a30cc51529220b66 1.16kB / 1.16kB 0.0s
=> => sha256:d73cf48caaac2e45ad76a2a9eb3b311d0e4eb1d804e3d2b9cf075a1fa31e6f92 46.04MB / 46.04MB 37.3s
=> => extracting sha256:1efc276f4ff952c055dea726cfc96ec6a4fdb8b62d9eed816bd2b788f2860ad7 1.0s
=> => extracting sha256:a2f2f93da48276873890ac821b3c991d53a7e864791aaf82c39b7863c908b93b 0.1s
=> => extracting sha256:12cca292b13cb58fadde25af113ddc4ac3b0c5e39ab3f1290a6ba62ec8237afd 0.0s
=> => extracting sha256:d73cf48caaac2e45ad76a2a9eb3b311d0e4eb1d804e3d2b9cf075a1fa31e6f92 0.7s
=> [builder 2/4] COPY . /root/iginx 1.3s
=> [builder 3/4] WORKDIR /root/iginx 0.1s
=> [builder 4/4] RUN mvn clean package -DskipTests -P-format 876.3s
=> [stage-1 2/2] COPY --from=builder /root/iginx/core/target/iginx-core-0.8.0 /iginx 0.2s
=> exporting to image 0.5s
=> => exporting layers 0.5s
=> => writing image sha256:e738348598c9db601dbf39c7a8ca9e1396c5ff51769afeb0fe3da12e2fdcd73a 0.0s
=> => naming to docker.io/library/iginx:0.6.0
Then start to run the image. Considering that IGinX and ZooKeeper communicates through network, it is necessary to establish a Docker network bridge to allow them to be interconnected through the network. Here we create a network bridge called docker-cluster-iginx:
$ docker network create -d bridge --attachable --subnet 172.40.0.0/16 docker-cluster-iginx
# 172.40.0.0 refers to the bridge's ip. You can customize it if necessary. The ip address usually starts with 172.
Now start Zookeeper:
$ cd ${zookeeper_path}
$ ./bin/zkServer.sh start
And then start an IoTDB instance:
$ cd ${iotdb_path}
# ./sbin/start-server.sh
Finally, start IGinX to complete the startup of the entire system:
$ cd ${iginx_path}/docker/onlyIginx
$ ./run_iginx_docker.sh x.x.x.x 10000
# x.x.x.x is the ip address IGinX container would use. It should be accessable to docker-cluster-iginx. You can use 172.40.0.2 for example. Note that 172.40.0.1 is the gateway and cannot be used here.
# 10000 refers to the port on host that can be used to access IGinX service. You can customize it if preferred.
This command will expose the localhost port 10000 as the communication interface with the IGinX cluster. You can start accessing IGinX through 127.0.0.1:10000.