It is useful to be able to delay state recovery until enough data nodes have joined the cluster, since this gives the shard allocator a decent opportunity to re-use as much existing data as possible. However we also have the option to delay state recovery until a certain number of master-eligible nodes have joined, and this seems unnecessary: we require a majority of master-eligible nodes for stat

英雄招募

成为 Doocs 项目维护者

本项目 advanced-java，包括 Doocs 开源组织下的所有项目，都欢迎各位朋友参与完善。

如果你提交的内容有价值，且具备规范性，将有机会提升为项目的维护者，直接参与项目的 review、merge 等维护工作，提交内容时也可以直接 push 到 doocs/advanced-java 主分支 master 下，无须提交 PR 等待 review。

目前 advanced-java 只有 [yanglbme](http

Hi,

It looks like some new metrics are now available via Cloudwatch for Route53Resolver, but the cloudwatch datasource doesn't support them yet. Can this be added please?

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/monitoring-resolver-with-cloudwatch.html

I can access these via AWS cli, but I can't see AWS/Route53Resolver namespace in my Grafana.

> aws cloudwatch li

There are a few places where we've missed strings that should be translated.

Here are a few that I've noticed:

• legend options https://github.com/elastic/kibana/blob/master/x-pack/legacy/plugins/canvas/public/lib/legend_options.js
• "No group" in filter group argument https://github.com/elastic/kibana/blob/9c1f5ae061cd005c1eebbdfa5d43465403bb146b/x-pack/legacy/plugins/canvas/canvas_

Hi,

I tried to enable the tls via default utility on free feature, but wasn't successful. Could you create a simple tutorial for this?

Along with the General Guides, it might be helpful to add a niche guide section, which is broken down by AWS service. Happy to issue a PR with some quality tutorials as an example.

What is the motivation for adding / enhancing this feature?

A tip on configuration for category url

What are the acceptance criteria

• Note a tip on configuration with respect to cate

Hi
I can't figure out how to index bolded field in this complex document. If you have to time to look, I appreciate.

data.docx

var doc = [{
id: 14,
name: "xxxxx",
code: "0001",
term: 1,
term_id: 1,
Programs: {
program_name: "Surgery",
Program_Kind: {

http://essql.nlpcn.org/ seems to be not working. Could you help me the page where can I get the full syntax for all supported queries like how to use

1. has_children
   2.has_parent,
2. like query (select * from index where field like 'test*'), here I need to use "test" as lower case and '*' which is not the same as sql.

As it's easier to see from images here are images of NewsBlur and InoReader. In a nutshell, the Inoreader shows the correct number of unread stories, but NewsBlur does not.

Both Feed Reader are marked unread yesterday at the same time.

NewsBlur:
See the yellow stories, that are somehow prefiltered (marked as read).
![2018-09-08 08_44_36-window](https://user-images.githubusercontent.com/116

Which version of Elastic are you using?

[x] elastic.v6 (for Elasticsearch 6.x)

Please describe the expected behavior

Get and update a document successed if its id contains both comma and slash.

Please describe the actual behavior

The es return 400 bad request error.

Any steps to reproduce the behavior?

Insert a document by bulk api , which id is "c7ccd3c6f4a7: <Mi

General information

• OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
• ElasticHQ Version: 3.2
• Elasticsearch Version: 5.6.4
• Python version: 3.4.6
• Browser Vendor and Version (if applicable): Chrome 62.*

Issue Description

indices detail page --> Administration ---> recommended add delete index function

Currently, the SerializationError and DeserializationError make easy to understand what went wrong, but not why.
The bad object/string is not part of the error, which makes more complex the debugging experience.

This can be easily improved by adding a data field to both the error classes:

class DeserializationError extends ElasticsearchClientError {
-  constructor (message) {

A quick way to tell that a query may be tuneable is if there's a Missing Index recommendation in the SqlPlan.

There's currently no indication of this either in the SQL Top Queries page or on the Query Detail itself, but it would be helpful to at least have an icon on the Top Queries page showing that there's something worth looking into. (I know that Index recommendations can be junk - that's w

Affected Projects
React

Is your feature request related to a problem? Please describe.
Was looking through the change log and the new documentation but could not find any reference to the deprecated DataController.

Describe the solution you'd like
Would be great to get some documentation on the recommended way to migrate from using DataController to not using it.

**Descr

From docs: "Range component containing only min/max input fields. Requires pressing "Go" to update the filter."

Why do all other inputs get searchOnChange? Including most Range Components!

I'm evaluating elasticsearch gui tools. Could you add a screenshot to the readme so people know what it looks like?