Elasticsearch集群上线经验技术点Welcome to my ELK world!(2)

1、安装win上的ELK(linux的和ubuntu的请参考个人另外一篇文章https://blog.51cto.com/13120271/2308902)
一、安装JDK,至少1.8.0_73以上版本,java -version
二、下载和解压缩Elasticsearch安装包,目录结构
三、启动Elasticsearch:bin\elasticsearch.bat,es自己特色之一就是开箱即用,若是是中小型应用,数据量少,操做不是很复杂,直接启动就能够用了java

四、检查ES是否启动成功:http://localhost:9200/?pretty
(资源包下载位置:https://pan.baidu.com/s/1tkygFTulBE-5Yypzt0CL8Q 密码:ygql)node

name: node名称
cluster_name: 集群名称(默认的集群名称就是elasticsearch)
version.number: 5.2.0,es版本号linux

{
"name" : "4onsTYV",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "nKZ9VK_vQdSQ1J0Dx9gx1Q",
"version" : {
"number" : "5.2.0",
"build_hash" : "24e05b9",
"build_date" : "2017-01-24T19:52:35.800Z",
"build_snapshot" : false,
"lucene_version" : "6.4.0"
},
"tagline" : "You Know, for Search"
}数据库

五、修改集群名称:elasticsearch.yml
六、下载和解压缩Kibana安装包,使用里面的开发界面,去操做elasticsearch,做为咱们学习es知识点的一个主要的界面入口
七、启动Kibana:bin\kibana.bat
八、进入Dev Tools界面
九、GET _cluster/healthjson

2、电商网站商品管理:集群健康检查ubuntu

一、document数据格式
二、电商网站商品管理案例:背景介绍
三、简单的集群管理
四、商品的CRUD操做(document CRUD操做)api


一、document数据格式数据结构

面向文档的搜索分析引擎elasticsearch

(1)应用系统的数据结构都是面向对象的,复杂的
(2)对象数据存储到数据库中,只能拆解开来,变为扁平的多张表,每次查询的时候还得还原回对象格式,至关麻烦
(3)ES是面向文档的,文档中存储的数据结构,与面向对象的数据结构是同样的,基于这种文档数据结构,es能够提供复杂的索引,全文检索,分析聚合等功能
(4)es的document用json数据格式来表达ide

public class Employee {

private String email;
private String firstName;
private String lastName;
private EmployeeInfo info;
private Date joinDate;

}

private class EmployeeInfo {

private String bio; // 性格
private Integer age;
private String[] interests; // 兴趣爱好

}

EmployeeInfo info = new EmployeeInfo();
info.setBio("curious and modest");
info.setAge(30);
info.setInterests(new String[]{"bike", "climb"});

Employee employee = new Employee();br/>employee.setEmail("zhangsan@sina.com");
employee.setFirstName("san");
employee.setLastName("zhang");
employee.setInfo(info);
employee.setJoinDate(new Date());

employee对象:里面包含了Employee类本身的属性,还有一个EmployeeInfo对象

两张表:employee表,employee_info表,将employee对象的数据从新拆开来,变成Employee数据和EmployeeInfo数据
employee表:email,first_name,last_name,join_date,4个字段
employee_info表:bio,age,interests,3个字段;此外还有一个外键字段,好比employee_id,关联着employee表

{
"email": "zhangsan@sina.com",
"first_name": "san",
"last_name": "zhang",
"info": {
"bio": "curious and modest",
"age": 30,
"interests": [ "bike", "climb" ]
},
"join_date": "2017/01/01"
}

咱们就明白了es的document数据格式和数据库的关系型数据格式的区别


二、电商网站商品管理案例背景介绍

有一个电商网站,须要为其基于ES构建一个后台系统,提供如下功能:

(1)对商品信息进行CRUD(增删改查)操做
(2)执行简单的结构化查询
(3)能够执行简单的全文检索,以及复杂的phrase(短语)检索
(4)对于全文检索的结果,能够进行高亮显示
(5)对数据进行简单的聚合分析


三、简单的集群管理

(1)快速检查集群的健康情况

es提供了一套api,叫作cat api,能够查看es中各类各样的数据

GET /_cat/health?v

epoch timestamp cluster status node.total node.data shards pri relo init unassign pending_tasks max_task_wait_time active_shards_percent
1488006741 15:12:21 elasticsearch yellow 1 1 1 1 0 0 1 0 - 50.0%

epoch timestamp cluster status node.total node.data shards pri relo init unassign pending_tasks max_task_wait_time active_shards_percent
1488007113 15:18:33 elasticsearch green 2 2 2 1 0 0 0 0 - 100.0%

epoch timestamp cluster status node.total node.data shards pri relo init unassign pending_tasks max_task_wait_time active_shards_percent
1488007216 15:20:16 elasticsearch yellow 1 1 1 1 0 0 1 0 - 50.0%

如何快速了解集群的健康情况?green、yellow、red?

green:每一个索引的primary shard和replica shard都是active状态的
yellow:每一个索引的primary shard都是active状态的,可是部分replica shard不是active状态,处于不可用的状态
red:不是全部索引的primary shard都是active状态的,部分索引有数据丢失了

为何如今会处于一个yellow状态?

咱们如今就一个笔记本电脑,就启动了一个es进程,至关于就只有一个node。如今es中有一个index,就是kibana本身内置创建的index。因为默认的配置是给每一个index分配5个primary shard和5个replica shard,并且primary shard和replica shard不能在同一台机器上(为了容错)。如今kibana本身创建的index是1个primary shard和1个replica shard。当前就一个node,因此只有1个primary shard被分配了和启动了,可是一个replica shard没有第二台机器去启动。

作一个小实验:此时只要启动第二个es进程,就会在es集群中有2个node,而后那1个replica shard就会自动分配过去,而后cluster status就会变成green状态。

(2)快速查看集群中有哪些索引

GET /_cat/indices?v

health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
yellow open .kibana rUm9n9wMRQCCrRDEhqneBg 1 1 1 0 3.1kb 3.1kb

(3)简单的索引操做

建立索引:PUT /test_index?pretty

health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
yellow open test_index XmS9DTAtSkSZSwWhhGEKkQ 5 1 0 0 650b 650b
yellow open .kibana rUm9n9wMRQCCrRDEhqneBg 1 1 1 0 3.1kb 3.1kb

删除索引:DELETE /test_index?pretty

health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
yellow open .kibana rUm9n9wMRQCCrRDEhqneBg 1 1 1 0 3.1kb 3.1kb


四、商品的CRUD操做

(1)新增商品:新增文档,创建索引

PUT /index/type/id
{
"json数据"
}

PUT /ecommerce/product/1
{
"name" : "gaolujie yagao",
"desc" : "gaoxiao meibai",
"price" : 30,
"producer" : "gaolujie producer",
"tags": [ "meibai", "fangzhu" ]
}

{
"_index": "ecommerce",
"_type": "product",
"_id": "1",
"_version": 1,
"result": "created",
"_shards": {
"total": 2,
"successful": 1,
"failed": 0
},
"created": true
}

PUT /ecommerce/product/2
{
"name" : "jiajieshi yagao",
"desc" : "youxiao fangzhu",
"price" : 25,
"producer" : "jiajieshi producer",
"tags": [ "fangzhu" ]
}

PUT /ecommerce/product/3
{
"name" : "zhonghua yagao",
"desc" : "caoben zhiwu",
"price" : 40,
"producer" : "zhonghua producer",
"tags": [ "qingxin" ]
}

es会自动创建index和type,不须要提早建立,并且es默认会对document每一个field都创建倒排索引,让其能够被搜索

(2)查询商品:检索文档

GET /index/type/id
GET /ecommerce/product/1

{
"_index": "ecommerce",
"_type": "product",
"_id": "1",
"_version": 1,
"found": true,
"_source": {
"name": "gaolujie yagao",
"desc": "gaoxiao meibai",
"price": 30,
"producer": "gaolujie producer",
"tags": [
"meibai",
"fangzhu"
]
}
}

(3)修改商品:替换文档

PUT /ecommerce/product/1
{
"name" : "jiaqiangban gaolujie yagao",
"desc" : "gaoxiao meibai",
"price" : 30,
"producer" : "gaolujie producer",
"tags": [ "meibai", "fangzhu" ]
}

{
"_index": "ecommerce",
"_type": "product",
"_id": "1",
"_version": 1,
"result": "created",
"_shards": {
"total": 2,
"successful": 1,
"failed": 0
},
"created": true
}

{
"_index": "ecommerce",
"_type": "product",
"_id": "1",
"_version": 2,
"result": "updated",
"_shards": {
"total": 2,
"successful": 1,
"failed": 0
},
"created": false
}

PUT /ecommerce/product/1
{
"name" : "jiaqiangban gaolujie yagao"
}

替换方式有一个很差,即便必须带上全部的field,才能去进行信息的修改

(4)修改商品:更新文档

POST /ecommerce/product/1/_update
{
"doc": {
"name": "jiaqiangban gaolujie yagao"
}
}

{
"_index": "ecommerce",
"_type": "product",
"_id": "1",
"_version": 8,
"result": "updated",
"_shards": {
"total": 2,
"successful": 1,
"failed": 0
}
}

个人风格,其实有选择的状况下,不太喜欢念ppt,或者照着文档作,或者直接粘贴写好的代码,尽可能是纯手敲代码

(5)删除商品:删除文档

DELETE /ecommerce/product/1

{
"found": true,
"_index": "ecommerce",
"_type": "product",
"_id": "1",
"_version": 9,
"result": "deleted",
"_shards": {
"total": 2,
"successful": 1,
"failed": 0
}
}

{"_index": "ecommerce","_type": "product","_id": "1","found": false}

相关文章
相关标签/搜索