ElasticSearch Index Name Must be Lowercase

After beating my head against the wall for a ridiculous amount of time, I still hadn't gotten a new logstash instance to put data into ElasticSearch. I had run the ELK stack before -- I was merely trying to use a new machine for the logstash instance and elasticsearch node.

After awhile it dawned on me that I should go check the ElasticSearch log. This is what I found, one entry for each time I fired up logstash:

[2014-12-01 10:35:27,478][DEBUG][action.admin.indices.create] [xended0590] [STAR20-2014.12.01] failed to create
org.elasticsearch.indices.InvalidIndexNameException: [STAR20-2014.12.01] Invalid index name [STAR20-2014.12.01], must be lowercase
at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService.validateIndexName(MetaDataCreateIndexService.java:182)
at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService.validate(MetaDataCreateIndexService.java:558)
at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService.access$200(MetaDataCreateIndexService.java:87)
at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService$2.execute(MetaDataCreateIndexService.java:243)
at org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.run(InternalClusterService.java:329)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:153)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

The key piece of information is in the second line:

org.elasticsearch.indices.InvalidIndexNameException: [STAR20-2014.12.01] Invalid index name [STAR20-2014.12.01], must be lowercase

(Despite the formatting above, this really is the second line of the log entry.)

*NIX, of course! And it's case-sensitivity.

Once I corrected this by changing the name of the index used within the logstash configuration file, things worked much better.

And, if you make changes to the ElasticSearch configuration file, don't forget to stop and restart ElasticSearch.

Comments

Post a Comment

Popular posts from this blog

Using Reference Aliases

Image
I recently ran across a situation where two different libraries shared identical namespaces and class names. Visual Studio complained anytime I used one of these classes that it was an ambiguous reference. I needed both libraries -- each contained some unique elements -- so I couldn't ditch one or the other. But, as I said, anytime I tried to use a class that was common (again, via the class name and namespace), I received the ambiguous reference error. This was a real problem, so say the least. However, C# provides a way to specify exactly which library (reference) you mean when you use an object that's common to two or more libraries. Simply put, you use an extern alias  statement. The concept is fairly simple: Give the reference an alias (I used the Properties windows for the reference). Add an extern alias statement, putting it before your using statements. Add a using statement, which effectively links a specific object through the extern alias statement to th
Read more

List of Visual Studio Keyboard Shortcuts

Here's a link to a great list of keyboard shortcuts for Visual Studio: 149 Shortcuts for Visual Studio 2015 (Windows) While there's no need to memorize the list (that's why someone has created a cheat sheet, after all), it certainly doesn't hurt to look over the list from time to time and try to add one more command to your repertoire.
Read more