# Elastic Search: Fix cluster health Red using JDBC River **URL:** \ **Category:** Elasticsearch\ **Created:** [May 2, 2015, 10:47am UTC](https://discuss.elastic.co/t/elastic-search-fix-cluster-health-red-using-jdbc-river/23517 "2015-05-02T10:47:55Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![James\_Crone](https://avatars.discourse-cdn.com/v4/letter/j/e68b1a/32.png) [@James\_Crone](https://discuss.elastic.co/u/James_Crone)\ **Post date:** [May 2, 2015, 10:47am UTC](https://discuss.elastic.co/t/elastic-search-fix-cluster-health-red-using-jdbc-river/23517/1 "2015-05-02T10:47:55Z")
Hello.. My Index Settings: PUT usersdata { "settings": { "index": { "number\_of\_shards": 3, "number\_of\_replicas": 2, "analysis": { "analyzer": { "analyzer\_keyword": { "tokenizer": "keyword", "filter": "lowercase" } } } } }, "mappings": { "users": { "properties": { "Name": { "analyzer": "analyzer\_keyword", "type": "string" } } } } } Index River JDBC Settings: POST \_river/usersdatariver/\_meta { "type" : "jdbc", "jdbc" : { "url" : "jdbc:mysql://localhost:3306/alterduden", "user" : "root", "password" : "", "poll" : "6s", "index" : "usersdata", "type" : "users", "schedule":"0/10 \* \* ? \* \*", "strategy" : "simple", "sql" : "select ID,Name,DateTime,First\_Name,Last\_Name,ID as \_id from users" } } I am using elasticsearch-1.5.0+marvel+elasticHQ plugins in LAN server but clustername and node name is different. When i create index its run fine for first time but when i restart elastic search status get RED. { "cluster\_name" : "mycluster", "status" : "red", "timed\_out" : false, "number\_of\_nodes" : 2, "number\_of\_data\_nodes" : 1, "active\_primary\_shards" : 6, "active\_shards" : 6, "relocating\_shards" : 0, "initializing\_shards" : 0, "unassigned\_shards" : 26, "number\_of\_pending\_tasks" : 0 } how to fix this problem? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/c8f33c6c-5e9e-4873-afcd-af9077825e64%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/c8f33c6c-5e9e-4873-afcd-af9077825e64%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [May 2, 2015, 7:42pm UTC](https://discuss.elastic.co/t/elastic-search-fix-cluster-health-red-using-jdbc-river/23517/2 "2015-05-02T19:42:56Z")
There should be error messages in the server log file of ES. Jörg On Sat, May 2, 2015 at 12:47 PM, James Crone [arafay696@gmail.com](mailto:arafay696@gmail.com) wrote: > Hello.. > > My Index Settings: > > PUT usersdata > { > "settings": { > "index": { > "number\_of\_shards": 3, > "number\_of\_replicas": 2, > "analysis": { > "analyzer": { > "analyzer\_keyword": { > "tokenizer": "keyword", > "filter": "lowercase" > } > } > } > } > }, > "mappings": { > "users": { > "properties": { > "Name": { > "analyzer": "analyzer\_keyword", > "type": "string" > } > } > } > } > } > > Index River JDBC Settings: > > POST \_river/usersdatariver/\_meta > { > "type" : "jdbc", > "jdbc" : { > "url" : "jdbc:mysql://localhost:3306/alterduden", > "user" : "root", > "password" : "", > "poll" : "6s", > "index" : "usersdata", > "type" : "users", > "schedule":"0/10 \* \* ? \* \*", > "strategy" : "simple", > "sql" : "select ID,Name,DateTime,First\_Name,Last\_Name,ID as \_id > from users" > } > } > > I am using elasticsearch-1.5.0+marvel+elasticHQ plugins in LAN server but > clustername and node name is different. When i create index its run fine > for first time but when i restart Elasticsearch status get RED. > > { > "cluster\_name" : "mycluster", > "status" : "red", > "timed\_out" : false, > "number\_of\_nodes" : 2, > "number\_of\_data\_nodes" : 1, > "active\_primary\_shards" : 6, > "active\_shards" : 6, > "relocating\_shards" : 0, > "initializing\_shards" : 0, > "unassigned\_shards" : 26, > "number\_of\_pending\_tasks" : 0 > } > > how to fix this problem? > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/c8f33c6c-5e9e-4873-afcd-af9077825e64%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/c8f33c6c-5e9e-4873-afcd-af9077825e64%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/c8f33c6c-5e9e-4873-afcd-af9077825e64%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/c8f33c6c-5e9e-4873-afcd-af9077825e64%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFvxCQqWE1DeKqDAp7sfnau5obJmTsn6Jr4b0feEZgPmw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFvxCQqWE1DeKqDAp7sfnau5obJmTsn6Jr4b0feEZgPmw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:16am UTC](https://discuss.elastic.co/t/elastic-search-fix-cluster-health-red-using-jdbc-river/23517/3 "2017-07-06T00:16:07Z")
Closed on July 6, 2017, 12:16am UTC