Elastic - Elastic Stack을 이용한 서울시 지하철 대시보드, 김종민님

URL : https://www.elastic.co/kr/blog/seoul-metro-2014

저도 한번 따라해보고 싶은 글입니다.

공유합니다

Elasticsearch 2016 conference videos

the 2016 Elasticsearch User Conference.

Full video : http://go.elastic.co/HM0030V0B4D1EMB0edA00Mp

I see the video contents log analytics

link : link

ElasticSearch Hardware recommendations

Source : https://www.elastic.co/guide/en/elasticsearch/guide/current/hardware.html

Memory

If you’ve been following the normal development path, you’ve probably been playing with Elasticsearch on your laptop or on a small cluster of machines laying around. But when it comes time to deploy Elasticsearch to production, there are a few recommendations that you should consider. Nothing is a hard-and-fast rule; Elasticsearch is used for a wide range of tasks and on a bewildering array of machines. But these recommendations provide good starting points based on our experience with production clusters.

In my computer environment,

CPUs

Most Elasticsearch deployments tend to be rather light on CPU requirements. As such, the exact processor setup matters less than the other resources. You should choose a modern processor with multiple cores. Common clusters utilize two to eight core machines.

If you need to choose between faster CPUs or more cores, choose more cores. The extra concurrency that multiple cores offers will far outweigh a slightly faster clock speed.

Network

A fast and reliable network is obviously important to performance in a distributed system. Low latency helps ensure that nodes can communicate easily, while high bandwidth helps shard movement and recovery. Modern data-center networking (1 GbE, 10 GbE) is sufficient for the vast majority of clusters.

Avoid clusters that span multiple data centers, even if the data centers are colocated in close proximity. Definitely avoid clusters that span large geographic distances.

Elasticsearch clusters assume that all nodes are equal—not that half the nodes are actually 150ms distant in another data center. Larger latencies tend to exacerbate problems in distributed systems and make debugging and resolution more difficult.

Similar to the NAS argument, everyone claims that their pipe between data centers is robust and low latency. This is true—until it isn’t (a network failure will happen eventually; you can count on it). From our experience, the hassle of managing cross–data center clusters is simply not worth the cost.

...

My server settings...

Mem : 1GB
CPU : 1 core
...
I can't use elasticsearch in my server.
:'-(

Install Elastic search + Logstash + Kibana

Install Elastic search + Logstash + Kibana on Ubuntu

0. ready to install
"it is recommended that you use the Oracle JDK version 1.8.0_25. Java installation varies from platform to platform" - elastic search 

1. files download
-Elastic search:
$curl -L -O https://download.elastic.co/elasticsearch/release/org/elasticsearch/distribution/tar/elasticsearch/2.1.1/elasticsearch-2.1.1.tar.gz

-Logstash:
$wget https://download.elastic.co/logstash/logstash/logstash-all-plugins-2.1.0.tar.gz

$wget
- Kibana:

$wget https://download.elastic.co/kibana/kibana/kibana-4.3.1-linux-x64.tar.gz

2. file extract

$tar -xvf elasticsearch-2.1.1.tar.gz

$tar -xvf logstash-all-plugins-2.1.0.tar.gz

$tar -xvf kibana-4.3.1-linux-x64.tar.gz