the default discovery settings are unsuitable for production use; at least one of [discovery.seed_ho

本文涉及的产品
检索分析服务 Elasticsearch 版,2核4GB开发者规格 1个月
简介: the default discovery settings are unsuitable for production use; at least one of [discovery.seed_ho
版本:7.17.5
错误信息:

ERROR: [1] bootstrap checks failed. You must address the points

described in the following [1] lines before starting Elasticsearch.

bootstrap check failure [1] of [1]: the default discovery settings are

unsuitable for production use; at least one of [discovery.seed_hosts,

discovery.seed_providers, cluster.initial_master_nodes] must be

configured ERROR: Elasticsearch did not exit normally - check the logs

at /usr/local/elasticsearch-7.17.5/logs/test-ES.log

解决方法:

到安装目录的config目录,编辑elasticsearch.yml

vim elasticsearch.yml

找到-------discovery-------,做如下修改


相关实践学习
使用阿里云Elasticsearch体验信息检索加速
通过创建登录阿里云Elasticsearch集群,使用DataWorks将MySQL数据同步至Elasticsearch,体验多条件检索效果,简单展示数据同步和信息检索加速的过程和操作。
ElasticSearch 入门精讲
ElasticSearch是一个开源的、基于Lucene的、分布式、高扩展、高实时的搜索与数据分析引擎。根据DB-Engines的排名显示,Elasticsearch是最受欢迎的企业搜索引擎,其次是Apache Solr(也是基于Lucene)。 ElasticSearch的实现原理主要分为以下几个步骤: 用户将数据提交到Elastic Search 数据库中 通过分词控制器去将对应的语句分词,将其权重和分词结果一并存入数据 当用户搜索数据时候,再根据权重将结果排名、打分 将返回结果呈现给用户 Elasticsearch可以用于搜索各种文档。它提供可扩展的搜索,具有接近实时的搜索,并支持多租户。
相关文章
|
10月前
|
监控 Dubbo 搜索推荐
No application config found or it‘s not a valid config! Please add <dubbo:application name=“...“ />
No application config found or it‘s not a valid config! Please add <dubbo:application name=“...“ />
1146 1
|
3月前
error: no configuration has been provided, try setting KUBERNETES_MASTER environment variable
error: no configuration has been provided, try setting KUBERNETES_MASTER environment variable
46 0
|
9月前
|
Java Spring
Spring Boot 启动报错解决:No active profile set, falling back to default profiles: default
Spring Boot 启动报错解决:No active profile set, falling back to default profiles: default
199 0
|
前端开发 开发工具
the default discovery settings are unsuitable for production use; at least one of [discovery.seed_ho
the default discovery settings are unsuitable for production use; at least one of [discovery.seed_ho
|
XML 应用服务中间件 数据格式
控制台报错: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting proper
控制台报错: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting proper
87 0
控制台报错: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting proper
|
Docker 容器
ERROR:the default discovery settings are unsuitable for production use
ERROR:the default discovery settings are unsuitable for production use
186 0
|
关系型数据库 MySQL
nodejs.ER_NOT_SUPPORTED_AUTH_MODEError: ER_NOT_SUPPORTED_AUTH_MODE:
nodejs.ER_NOT_SUPPORTED_AUTH_MODEError: ER_NOT_SUPPORTED_AUTH_MODE:
107 0
Embedded web server initialization - jar file default-mimetypes.properties
Embedded web server initialization - jar file default-mimetypes.properties
112 0
Embedded web server initialization - jar file default-mimetypes.properties
metadata request forward to GM6 - X-DevTools-Emulate-Network-Conditions-Cli
metadata request forward to GM6 - X-DevTools-Emulate-Network-Conditions-Cli
102 0
metadata request forward to GM6 - X-DevTools-Emulate-Network-Conditions-Cli
how does gateway framework treat default system flag in customizing
Suppose we have maintain multiple backend system as “default” in customizing:
124 0
how does gateway framework treat default system flag in customizing