`

es recover

 
阅读更多
on log operations
2015-07-01 14:33:09,517 TRACE indices.recovery: [15] [yotta-20150629][23] no translog operations (id: [1435590963614]) to send to [14][uwra9okWTSOVARg5QqTbxA][centos-14][inet[/192.168.1.14:9300]]
2015-07-01 14:33:09,517 TRACE indices.recovery: [15] [yotta-20150629][23] sending final batch of [0][0b] (total: [0], id: [1435590963614]) translog operations to [14][uwra9okWTSOVARg5QqTbxA][centos-14][inet[/192.168.1.14:9300]]
2015-07-01 14:33:09,517 TRACE indices.recovery: [15] [yotta-20150629][23] recovery [phase2] to [14][uwra9okWTSOVARg5QqTbxA][centos-14][inet[/192.168.1.14:9300]]: took [213.7micros]
2015-07-01 14:33:09,517 TRACE indices.recovery: [15] [yotta-20150629][23] recovery [phase3] to [14][uwra9okWTSOVARg5QqTbxA][centos-14][inet[/192.168.1.14:9300]]: sending transaction log operations
2015-07-01 14:33:09,517 TRACE indices.recovery: [15] [yotta-20150629][23] no translog operations (id: [1435590963614]) to send to [14][uwra9okWTSOVARg5QqTbxA][centos-14][inet[/192.168.1.14:9300]]
2015-07-01 14:33:09,517 TRACE indices.recovery: [15] [yotta-20150629][23] sending final batch of [0][0b] (total: [0], id: [1435590963614]) translog operations to [14][uwra9okWTSOVARg5QqTbxA][centos-14][inet[/192.168.1.14:9300]]
2015-07-01 14:33:09,519 TRACE indices.recovery: [15] [yotta-20150629][23] recovery [phase3] to [14][uwra9okWTSOVARg5QqTbxA][centos-14][inet[/192.168.1.14:9300]]: took [2.1ms]
2015-07-01 14:33:09,536 DEBUG zen.publish: [15] received cluster state version 1208
2015-07-01 14:33:09,790 DEBUG zen.publish: [15] received cluster state version 1209
2015-07-01 14:34:29,185 DEBUG index.engine: [15] [yotta-20150629][9] [[yotta-20150629][9]] skipping check for 3x segments
2015-07-01 14:34:29,511 DEBUG index.shard: [15] [yotta-20150629][9] scheduling refresher every 30s
2015-07-01 14:34:29,524 TRACE indices.recovery: [15] [yotta-20150629][9] marking recovery from [16][8-B6KcSJRhqI91HTrlf_hw][centos-16][inet[/192.168.1.16:9300]] as done, id [50]
2015-07-01 14:34:29,525 DEBUG index.shard: [15] [yotta-20150629][9] state: [RECOVERING]->[POST_RECOVERY], reason [peer recovery done]
2015-07-01 14:34:29,525 DEBUG action.shard: [15] sending shard started for [yotta-20150629][9], node[L2qO9dkLSnuByemxYMdx-A], [R], s[INITIALIZING], indexUUID [FH4DRptCS6K3cpDV54Q9ww], reason [after recovery (replica) from node [[16][8-B6KcSJRhqI91HTrlf_hw][centos-16][inet[/192.168.1.16:9300]]]]
2015-07-01 14:34:29,525 TRACE indices.recovery: [15] [yotta-20150629][9] recovery completed from [16][8-B6KcSJRhqI91HTrlf_hw][centos-16][inet[/192.168.1.16:9300]], took[3.4m]
   phase1: recovered_files [293] with total_size of [14.8gb], took [3.4m], throttling_wait [0s]
         : reusing_files   [0] with total_size of [0b]
   phase2: start took [326ms]
         : recovered [0] transaction log operations, took [0s]
   phase3: recovered [0] transaction log operations, took [1ms]
2015-07-01 14:34:29,532 DEBUG zen.publish: [15] received cluster state version 1210
2015-07-01 14:34:29,538 DEBUG index.shard: [15] [yotta-20150629][9] state: [POST_RECOVERY]->[STARTED], reason [global state is [STARTED]]
2015-07-01 14:34:49,982 TRACE indices.recovery: [15] [yotta-20150629][1] recovery [phase1] to [16][8-B6KcSJRhqI91HTrlf_hw][centos-16][inet[/192.168.1.16:9300]]: took [3.7m]
2015-07-01 14:34:49,982 TRACE indices.recovery: [15] [yotta-20150629][1] recovery [phase2] to [16][8-B6KcSJRhqI91HTrlf_hw][centos-16][inet[/192.168.1.16:9300]]: start
2015-07-01 14:34:51,452 TRACE indices.recovery: [15] [yotta-20150629][1] recovery [phase2] to [16][8-B6KcSJRhqI91HTrlf_hw][centos-16][inet[/192.168.1.16:9300]]: start took [1.4s]
2015-07-01 14:34:51,452 TRACE indices.recovery: [15] [yotta-20150629][1] recovery [phase2] to [16][8-B6KcSJRhqI91HTrlf_hw][centos-16][inet[/192.168.1.16:9300]]: updating current mapping to master
2015-07-01 14:34:51,454 TRACE indices.recovery: [15] [yotta-20150629][1] recovery [phase2] to [16][8-B6KcSJRhqI91HTrlf_hw][centos-16][inet[/192.168.1.16:9300]]: sending transaction log operations
2015-07-01 14:34:51,454 TRACE indices.recovery: [15] [yotta-20150629][1] no translog operations (id: [1435591003054]) to send to [16][8-B6KcSJRhqI91HTrlf_hw][centos-16][inet[/192.168.1.16:9300]]
2015-07-01 14:34:51,454 TRACE indices.recovery: [15] [yotta-20150629][1] sending final batch of [0][0b] (total: [0], id: [1435591003054]) translog operations to [16][8-B6KcSJRhqI91HTrlf_hw][centos-16][inet[/192.168.1.16:9300]]
2015-07-01 14:34:51,455 TRACE indices.recovery: [15] [yotta-20150629][1] recovery [phase2] to [16][8-B6KcSJRhqI91HTrlf_hw][centos-16][inet[/192.168.1.16:9300]]: took [377.9micros]
2015-07-01 14:34:51,455 TRACE indices.recovery: [15] [yotta-20150629][1] recovery [phase3] to [16][8-B6KcSJRhqI91HTrlf_hw][centos-16][inet[/192.168.1.16:9300]]: sending transaction log operations
2015-07-01 14:34:51,455 TRACE indices.recovery: [15] [yotta-20150629][1] no translog operations (id: [1435591003054]) to send to [16][8-B6KcSJRhqI91HTrlf_hw][centos-16][inet[/192.168.1.16:9300]]
2015-07-01 14:34:51,455 TRACE indices.recovery: [15] [yotta-20150629][1] sending final batch of [0][0b] (total: [0], id: [1435591003054]) translog operations to [16][8-B6KcSJRhqI91HTrlf_hw][centos-16][inet[/192.168.1.16:9300]]
2015-07-01 14:34:51,457 TRACE indices.recovery: [15] [yotta-20150629][1] recovery [phase3] to [16][8-B6KcSJRhqI91HTrlf_hw][centos-16][inet[/192.168.1.16:9300]]: took [1.8ms]
2015-07-01 14:34:51,484 DEBUG zen.publish: [15] received cluster state version 1211
分享到：
记录记录
评论
发表评论

您还没有登录,请您登录后再发表评论

相关推荐

    最新版linux elasticsearch-8.2.3-linux-x86_64.tar.gz

    Elasticsearch是一个开源的全文搜索引擎，它基于Lucene构建，被广泛用于实时数据分析、日志聚合、搜索引擎等场景。在Linux环境下，Elasticsearch的安装和管理是一项基础但至关重要的任务。最新版的Elasticsearch为...

    elasticsearch集群安装包

    在本篇中，我们将深入探讨如何进行 Elasticsearch（简称 ES）集群的安装。 首先，了解集群的概念至关重要。在 Elasticsearch 中，集群是一组节点（运行 Elasticsearch 的服务器），它们共同存储数据并处理搜索和...

    Monitoring ElasticSearch

    Understand common performance and reliability pitfalls in ElasticSearch Use popular monitoring tools such as ElasticSearch-head, BigDesk, Marvel, Kibana, and more This is a step-by-step guide with ...

    Elasticsearch主备集群.docx

    Elasticsearch主备集群搭建与配置详解 Elasticsearch 是一款功能强大的开源搜索引擎，广泛应用于日志分析、全文检索和实时数据分析等领域。构建一个主备集群可以提高数据的可用性和可靠性，确保在主节点出现问题时...

    英文原版-Monitoring ElasticSearch 1st Edition

    Monitor your Elasticsearch cluster's health, and diagnose and solve its performance and reliability issuesElasticSearch is a distributed search server similar to Apache Solr with a focus on large ...

    Elasticsearch优化1

    在本文中，我们将深入探讨Elasticsearch的优化策略，这些策略涵盖了内存管理、系统配置、索引设置、集群通信和数据恢复等多个方面。Elasticsearch是一个高性能的全文搜索引擎，优化其性能对于提升系统的整体效率至关...

    linux下安装ES.txt

    ### Linux环境下安装Elasticsearch详解 #### 一、环境准备与用户配置 在开始安装Elasticsearch之前，首先需要在Linux环境下做好相应的环境准备。这包括创建必要的用户组及用户，并进行权限设置。 1. **创建用户组...

    ES优化1

    Elasticsearch(ES) 是一款高性能的全文搜索引擎，广泛应用于数据分析和实时检索场景。在构建生产级别的ES集群时，优化配置至关重要，以确保系统的稳定性和高效性。以下是一些关键的ES集群配置优化要点： 1. **主机...

    Elastice search 的使用1

    Elasticsearch 是一个分布式、实时的搜索和分析引擎，常用于海量数据的处理和分析，尤其是在日志聚合和实时检索方面表现出色。本篇主要讨论如何有效地使用 Elasticsearch 处理大规模数据，包括硬件配置、数据接入、...

    Recover Password Plc Delta.zip_Crack delta_PLC password crack_cr

    Crack password for PLC Delta Series ES, EH

    Réparer_Données_Table_paradoxdatabase_

    标题中的“Réparer_Données_Table_paradoxdatabase_”暗示了这是一个关于修复Paradox数据库中数据表的问题。Paradox是一种流行的数据库管理系统，尤其在早期的个人计算机领域中广泛使用。它由Borland公司开发，...

    CrateDB单节点部署，集群部署，配置文件详解，问题解决及优化

    该数据库底层采用了Elasticsearch的部分源代码，并在此基础上进行了改进，使之不仅支持SQL语法，还解决了Elasticsearch不支持多表连接的问题，使得数据查询更加灵活便捷。 #### 二、CrateDB的安装与配置 ##### 2.1...

    Go语言中文文档高清版

    * ETCD、Kafka、RabbitMQ、ElasticSearch等 八、框架和库 * Beego框架：安装、配置、路由、控制器、模型、视图等 * Gin框架：安装、路由、控制器、模型、视图等 * GORM数据库 ORM 框架 * xorm数据库 ORM 框架 九...

    神器mimikatz_trunk

    Message du processus :Bienvenue dans un processus distant Gentil KiwiSekurLSA : librairie de manipulation des données de sécurités dans LSASSmimikatz # @getLogonPasswordsAuthentification Id : 0;...

    全志A10 说明

    - **图形处理单元(GPU)**：内置Mali系列GPU，支持OpenGL ES 2.0。 - **内存**：DDR3高速内存，最大支持1GB。 - **存储**：支持NAND Flash、SD/MMC卡等多种存储介质。 - **网络接口**：集成百兆以太网控制器。 - **...

    go web编程

    ### Go Web 编程知识点概览 #### 一、Go Web 编程简介与环境配置 **1.1 Go 安装** ...- **panic 和 recover**：处理运行时错误的方法。 - **延迟调用**：使用 `defer` 关键字推迟执行函数。 **11.2 使用...

Magicbox
Global site tag (gtag.js) - Google Analytics