a7fa5eb634
Non-raft nodes need to be notifified when the metastore changes. For example, a database could be dropped on node 1 (non-raft) and node 2 would not know. Since queries for that database would not be a cache miss, node 2 would not get updated. To propogate changes to non-raft nodes, each non-raft node maintains a blocking connection to a raft node that blocks until a metadata change occurs. When the change is triggered, the updated metadata is returned to the client and the client idempotently updates its local cache. It then reconnects and waits for another change. This is similar watches in zookeeper or etcd. Since the blocking request is always recreated, it also serves as a polling mechanism that will retry another raft member if the current connection is lost. |
||
|---|---|---|
| .hooks | ||
| client | ||
| cluster | ||
| cmd | ||
| etc | ||
| influxql | ||
| meta | ||
| scripts | ||
| services | ||
| shared/admin | ||
| snapshot | ||
| statik | ||
| tcp | ||
| tests | ||
| toml | ||
| tsdb | ||
| uuid | ||
| .gitignore | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| QUERIES.md | ||
| README.md | ||
| balancer.go | ||
| balancer_test.go | ||
| circle-test.sh | ||
| circle.yml | ||
| diagnostics.go | ||
| errors.go | ||
| nightly.sh | ||
| package.sh | ||
README.md
InfluxDB 
An Open-Source, Distributed, Time Series Database
InfluxDB v0.9.0 is now out. Going forward, the 0.9.x series of releases will not make breaking API changes or breaking changes to the underlying data storage. However, 0.9.0 clustering should be considered an alpha release.
InfluxDB is an open source distributed time series database with no external dependencies. It's useful for recording metrics, events, and performing analytics.
Features
- Built-in HTTP API so you don't have to write any server side code to get up and running.
- Clustering is supported out of the box, so that you can scale horizontally to handle your data.
- Simple to install and manage, and fast to get data in and out.
- It aims to answer queries in real-time. That means every data point is indexed as it comes in and is immediately available in queries that should return in < 100ms.
Getting Started
The following directions apply only to the 0.9.0 release or building from the source on master.
Building
You don't need to build the project to use it - you can use any of our pre-built packages to install InfluxDB. That's the recommended way to get it running. However, if you want to contribute to the core of InfluxDB, you'll need to build. For those adventurous enough, you can follow along on our docs.
Starting InfluxDB
service influxdb startif you have installed InfluxDB using an official Debian or RPM package.$GOPATH/bin/influxdif you have built InfluxDB from source.
Creating your first database
curl -G 'http://localhost:8086/query' --data-urlencode "q=CREATE DATABASE mydb"
Insert some data
curl -XPOST 'http://localhost:8086/write?db=mydb' \
-d 'cpu,host=server01,region=uswest value=1.0 1434055562000000000'
Query for the data
curl -G http://localhost:8086/query?pretty=true --data-urlencode "db=mydb" \
--data-urlencode "q=SELECT * FROM cpu WHERE host='server01'"
Helpful Links
- Understand the design goals and motivations of the project.
- Follow the getting started guide to find out how to install InfluxDB, start writing more data, and issue more queries - in just a few minutes.
- See the HTTP API documentation to start writing a library for your favorite language.