ElasticHD 是一款 ElasticSearch的可视化应用。不依赖ES的插件安装，更便捷；导航栏直接填写对应的ES IP和端口就可以操作Es了。目前支持如下功能：

•  ES Real time data search
•  ES Dashboard data visualization
•  ES Index Template (在线修改、查看、上传）
•  ES Indices Index deletion and search
•  SQL Converts to Elasticsearch DSL
•  ES 基本查询文档

•   linux and MacOs use ElasticHD

1. 下载对应的elasticHD版本，unzip xxx_elasticHd_xxx.zip 
2. 修改权限 chmod 0777 ElasticHD 
3. 可指定ip端口运行elastichd ./ElasticHD -p 127.0.0.1:9800 默认 ip和端口也是这个

•  windows use ElasticHD 
• 直接下载对应windows版本,解压，双击运行。当然想指定端口的话同linux

1. 修复 bug，单分片进行 scroll 操作可能引起 X-Pack Security 造成节点僵死及 OOM。
2. Elasticsearch 5.4.0 启用 TLS 不能对 5.3.x 和之前的节点进行认证。
3. LDAP 认证用户在撤销认证之后后可能任然驻留在缓存。
4. 现在，Netty在处理线程池、缓冲池和其他资源时，尊重处理器的设置，而不是在其他容器上运行时，可能会对这些资源进行过度的调整。
5. 对关闭的索引进行 Index setting 修改将进行验证，保护因为错误的配置造成索引无法打开的问题。
6. 修复 TransportClient 关于嗅探可能造成客户端挂起的异常。
7. 修复在KERBEROS安全模式，HDFS repository 插件与 Java Security Manager 发生的冲突。
8. 修复 Snapshot/restore 在 Elasticsearch 5.2.x 及之前的版本在取回所有快照时异常缓慢的问题。

• Debugging Java Native Memory Leaks
• Tracking Down Native Memory Leaks in Elasticsearch
• CompressingStoredFieldsFormat should reclaim memory more aggressively
• Close InputStream when receiving cluster state in PublishClusterStateAction
• Kafka OOM During Log Recovery Due to Leaked Native Memory

POST test_index/type1/?refresh=true

{

  "foo": "bar"

}

POST /test_index/_search

{

  "query": {

    "wildcard": {

      "foo": {

        "value": "*在迪士尼乐园，点亮心中奇梦。它是一个充满创造力、冒险精神与无穷精彩的快地。您可在此游览全球最大的迪士尼城堡——奇幻童话城堡，探索别具一格又令人难忘的六大主题园区——米奇大街、奇想花园、梦幻世界、探险岛、宝藏湾和明日世界，和米奇朋友在一起，感觉欢乐时光开业于2016年上海国际旅游度假区秀沿路亚朵酒店位于上海市浦东新区沪南公路（沪南公路与秀沿路交汇处），临近周浦万达广场、地铁11号线秀沿路站，距离上海南站、人民广场约20公里，距离迪线距*"

      }

    }

  }

}

{

  "took": 3445,

  "timed_out": false,

  "_shards": {

    "total": 5,

    "successful": 5,

    "failed": 0

  },

  "hits": {

    "total": 0,

    "max_score": null,

    "hits": 

  }

}

 
Caused by: org.apache.lucene.util.automaton.TooComplexToDeterminizeException: Determinizing automaton with 22082 states and 34182 transitions would result in more than 10000 states. at org.apache.lucene.util.automaton.Operations.determinize(Operations.java:741) ~[lucene-core-6.4.1.jar:6.4.1
 

public static Automaton toAutomaton(Term wildcardquery) {

    List<Automaton> automata = new ArrayList<>();

    

    String wildcardText = wildcardquery.text();

    

    for (int i = 0; i < wildcardText.length();) {

      final int c = wildcardText.codePointAt(i);

      int length = Character.charCount(c);

      switch(c) {

        case WILDCARD_STRING: 

          automata.add(Automata.makeAnyString());

          break;

        case WILDCARD_CHAR:

          automata.add(Automata.makeAnyChar());

          break;

        case WILDCARD_ESCAPE:

          // add the next codepoint instead, if it exists

          if (i + length < wildcardText.length()) {

            final int nextChar = wildcardText.codePointAt(i + length);

            length += Character.charCount(nextChar);

            automata.add(Automata.makeChar(nextChar));

            break;

          } // else fallthru, lenient parsing with a trailing \

        default:

          automata.add(Automata.makeChar(c));

      }

      i += length;

    }

    

    return Operations.concatenate(automata);

  }

/**

   * Determinizes the given automaton.

   * <p>

   * Worst case complexity: exponential in number of states.

   * @param maxDeterminizedStates Maximum number of states created when

   *   determinizing.  Higher numbers allow this operation to consume more

   *   memory but allow more complex automatons.  Use

   *   DEFAULT_MAX_DETERMINIZED_STATES as a decent default if you don't know

   *   how many to allow.

   * @throws TooComplexToDeterminizeException if determinizing a creates an

   *   automaton with more than maxDeterminizedStates

   */

  public static Automaton determinize(Automaton a, int maxDeterminizedStates) {

  /**

   * Default maximum number of states that {@link Operations#determinize} should create.

   */

  public static final int DEFAULT_MAX_DETERMINIZED_STATES = 10000;

" Note that this query can be slow, as it needs to iterate over many terms. In order to prevent extremely slow wildcard queries, a wildcard term should not start with one of the wildcards * or ?."