Re: ElasticsearchIllegalArgumentException can't parse config file

2015-01-26 Thread David Pilato 
Could you test this config locally and add one setting at a time and check 
which one is incorrect?

--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

> Le 27 janv. 2015 à 06:39, Xavier Garcia  a écrit :
> 
> Any idea ? Someone know if a configuration validator exist for ElasticSearch? 
> Or how i can improve the loggin to find which line it's
> 
> Thank you,
> 
> Le lundi 26 janvier 2015 15:13:09 UTC-8, Xavier Garcia a écrit :
>> 
>> Yep False so and rewrite all number i can, change the charset of file. It's 
>> crasy i don't understabd what happend.
>> 
>> Le lundi 26 janvier 2015 14:32:40 UTC-8, David Pilato a écrit :
>>> 
>>> Of course, you did it for False as well?
>>> 
>>> 
>>> David
>>> 
 Le 26 janv. 2015 à 23:14, Xavier Garcia  a écrit :
 
 Already try but doesn't work.
 
 Le lundi 26 janvier 2015 14:08:39 UTC-8, David Pilato a écrit :
> 
> Could you try replacing True by true?
> 
> David
> 
>> Le 26 janv. 2015 à 22:49, Xavier Garcia  a écrit :
>> 
>> Hello guy,
>> 
>> I'm configuring a ES cluster and i got this issue - 
>> ElasticsearchIllegalArgumentException[value cannot be parsed to boolean 
>> [ true/1/on/yes OR false/0/off/no ]  ]
>> I try to increase the level of logging but nothing work i can't find the 
>> right line, do you have any idea where is this value in my config file ?
>> 
>> Thank you
>> 
>> 
>> cluster.name: Cluster-Production
>> node.name: elastic2.cluster.net
>> node.master: True
>> node.rack: ec2
>> node.max_local_storage_nodes: 1
>> node.data: /srv/data/elasticsearch
>> index.mapper_dynamic: True
>> index.query.bool.max_clause_count: 4096
>> path.conf: /srv/conf/elasticsearch
>> path.data: /srv/data/elasticsearch
>> path.logs: /srv/logs/elasticsearch
>> path.plugins: /srv/app/elasticsearch/plugins
>> bootstrap.mlockall: True
>> transport.tcp.port: 9300
>> http.port: 9200
>> http.enabled: True
>> gateway.type: local
>> gateway.recover_after_nodes: 1
>> gateway.recover_after_time: 2m
>> gateway.expected_nodes: 1
>> discovery.zen.minimum_master_nodes: 1
>> discovery.zen.ping.timeout: 30s
>> discovery.zen.ping.multicast.enabled: False
>> discovery.zen.ping.unicast.hosts: ["elastic1.internal.cluster.net", 
>> "elastic2.internal.cluster.net", "elastic3.internal.cluster.net", 
>> "elastic4.internal.cluster.net", "elastic5.internal.cluster.net"]
>> action.auto_create_index: True
>> action.disable_delete_all_indices: True
>> script.disable_dynamic: False
>> threadpool.bulk.type: fixed
>> threadpool.bulk.size: 50
>> threadpool.bulk.queue_size: 1000
>> -- 
>> 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 elasticsearc...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/f724407f-6163-4433-9dd7-5c8c66fcece2%40googlegroups.com.
>> For more options, visit 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 elasticsearc...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/elasticsearch/44b06669-bb82-4275-acdf-e8fdabc95c06%40googlegroups.com.
 For more options, visit 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/elasticsearch/5da68ec9-e7c8-4dda-ba36-732919e9cd8e%40googlegroups.com.
> For more options, visit 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/B25CCF9B-5C12-4A26-ADEA-8F9C54ADA63E%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Re: ElasticsearchIllegalArgumentException can't parse config file

2015-01-26 Thread Xavier Garcia 
Any idea ? Someone know if a configuration validator exist for 
ElasticSearch? Or how i can improve the loggin to find which line it's

Thank you,

Le lundi 26 janvier 2015 15:13:09 UTC-8, Xavier Garcia a écrit :
>
> Yep False so and rewrite all number i can, change the charset of file. 
> It's crasy i don't understabd what happend.
>
> Le lundi 26 janvier 2015 14:32:40 UTC-8, David Pilato a écrit :
>>
>> Of course, you did it for False as well?
>>
>>
>> David
>>
>> Le 26 janv. 2015 à 23:14, Xavier Garcia  a écrit :
>>
>> Already try but doesn't work.
>>
>> Le lundi 26 janvier 2015 14:08:39 UTC-8, David Pilato a écrit :
>>>
>>> Could you try replacing True by true?
>>>
>>> David
>>>
>>> Le 26 janv. 2015 à 22:49, Xavier Garcia  a écrit :
>>>
>>> Hello guy,
>>>
>>> I'm configuring a ES cluster and i got this issue - 
>>> *ElasticsearchIllegalArgumentException[value 
>>> cannot be parsed to boolean [ true/1/on/yes OR false/0/off/no ]  ]*
>>> I try to increase the level of logging but nothing work i can't find the 
>>> right line, do you have any idea where is this value in my config file ?
>>>
>>> Thank you
>>>
>>>
>>> cluster.name: Cluster-Production
>>> node.name: elastic2.cluster.net
>>> node.master: True
>>> node.rack: ec2
>>> node.max_local_storage_nodes: 1
>>> node.data: /srv/data/elasticsearch
>>> index.mapper_dynamic: True
>>> index.query.bool.max_clause_count: 4096
>>> path.conf: /srv/conf/elasticsearch
>>> path.data: /srv/data/elasticsearch
>>> path.logs: /srv/logs/elasticsearch
>>> path.plugins: /srv/app/elasticsearch/plugins
>>> bootstrap.mlockall: True
>>> transport.tcp.port: 9300
>>> http.port: 9200
>>> http.enabled: True
>>> gateway.type: local
>>> gateway.recover_after_nodes: 1
>>> gateway.recover_after_time: 2m
>>> gateway.expected_nodes: 1
>>> discovery.zen.minimum_master_nodes: 1
>>> discovery.zen.ping.timeout: 30s
>>> discovery.zen.ping.multicast.enabled: False
>>> discovery.zen.ping.unicast.hosts: ["elastic1.internal.cluster.net", "
>>> elastic2.internal.cluster.net", "elastic3.internal.cluster.net", "
>>> elastic4.internal.cluster.net", "elastic5.internal.cluster.net"]
>>> action.auto_create_index: True
>>> action.disable_delete_all_indices: True
>>> script.disable_dynamic: False
>>> threadpool.bulk.type: fixed
>>> threadpool.bulk.size: 50
>>> threadpool.bulk.queue_size: 1000
>>>
>>> -- 
>>> 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 elasticsearc...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/elasticsearch/f724407f-6163-4433-9dd7-5c8c66fcece2%40googlegroups.com
>>>  
>>> 
>>> .
>>> For more options, visit 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 elasticsearc...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/44b06669-bb82-4275-acdf-e8fdabc95c06%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/5da68ec9-e7c8-4dda-ba36-732919e9cd8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ElasticsearchIllegalArgumentException can't parse config file

2015-01-26 Thread Xavier Garcia 
Yep False so and rewrite all number i can, change the charset of file. It's 
crasy i don't understabd what happend.

Le lundi 26 janvier 2015 14:32:40 UTC-8, David Pilato a écrit :
>
> Of course, you did it for False as well?
>
>
> David
>
> Le 26 janv. 2015 à 23:14, Xavier Garcia > a 
> écrit :
>
> Already try but doesn't work.
>
> Le lundi 26 janvier 2015 14:08:39 UTC-8, David Pilato a écrit :
>>
>> Could you try replacing True by true?
>>
>> David
>>
>> Le 26 janv. 2015 à 22:49, Xavier Garcia  a écrit :
>>
>> Hello guy,
>>
>> I'm configuring a ES cluster and i got this issue - 
>> *ElasticsearchIllegalArgumentException[value 
>> cannot be parsed to boolean [ true/1/on/yes OR false/0/off/no ]  ]*
>> I try to increase the level of logging but nothing work i can't find the 
>> right line, do you have any idea where is this value in my config file ?
>>
>> Thank you
>>
>>
>> cluster.name: Cluster-Production
>> node.name: elastic2.cluster.net
>> node.master: True
>> node.rack: ec2
>> node.max_local_storage_nodes: 1
>> node.data: /srv/data/elasticsearch
>> index.mapper_dynamic: True
>> index.query.bool.max_clause_count: 4096
>> path.conf: /srv/conf/elasticsearch
>> path.data: /srv/data/elasticsearch
>> path.logs: /srv/logs/elasticsearch
>> path.plugins: /srv/app/elasticsearch/plugins
>> bootstrap.mlockall: True
>> transport.tcp.port: 9300
>> http.port: 9200
>> http.enabled: True
>> gateway.type: local
>> gateway.recover_after_nodes: 1
>> gateway.recover_after_time: 2m
>> gateway.expected_nodes: 1
>> discovery.zen.minimum_master_nodes: 1
>> discovery.zen.ping.timeout: 30s
>> discovery.zen.ping.multicast.enabled: False
>> discovery.zen.ping.unicast.hosts: ["elastic1.internal.cluster.net", "
>> elastic2.internal.cluster.net", "elastic3.internal.cluster.net", "
>> elastic4.internal.cluster.net", "elastic5.internal.cluster.net"]
>> action.auto_create_index: True
>> action.disable_delete_all_indices: True
>> script.disable_dynamic: False
>> threadpool.bulk.type: fixed
>> threadpool.bulk.size: 50
>> threadpool.bulk.queue_size: 1000
>>
>> -- 
>> 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 elasticsearc...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/f724407f-6163-4433-9dd7-5c8c66fcece2%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit 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 elasticsearc...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/elasticsearch/44b06669-bb82-4275-acdf-e8fdabc95c06%40googlegroups.com
>  
> 
> .
> For more options, visit 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/0ded5242-8e69-4d21-a954-8807a3295791%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ElasticsearchIllegalArgumentException can't parse config file

2015-01-26 Thread David Pilato 
Of course, you did it for False as well?


David

> Le 26 janv. 2015 à 23:14, Xavier Garcia  a écrit :
> 
> Already try but doesn't work.
> 
> Le lundi 26 janvier 2015 14:08:39 UTC-8, David Pilato a écrit :
>> 
>> Could you try replacing True by true?
>> 
>> David
>> 
>>> Le 26 janv. 2015 à 22:49, Xavier Garcia  a écrit :
>>> 
>>> Hello guy,
>>> 
>>> I'm configuring a ES cluster and i got this issue - 
>>> ElasticsearchIllegalArgumentException[value cannot be parsed to boolean [ 
>>> true/1/on/yes OR false/0/off/no ]  ]
>>> I try to increase the level of logging but nothing work i can't find the 
>>> right line, do you have any idea where is this value in my config file ?
>>> 
>>> Thank you
>>> 
>>> 
>>> cluster.name: Cluster-Production
>>> node.name: elastic2.cluster.net
>>> node.master: True
>>> node.rack: ec2
>>> node.max_local_storage_nodes: 1
>>> node.data: /srv/data/elasticsearch
>>> index.mapper_dynamic: True
>>> index.query.bool.max_clause_count: 4096
>>> path.conf: /srv/conf/elasticsearch
>>> path.data: /srv/data/elasticsearch
>>> path.logs: /srv/logs/elasticsearch
>>> path.plugins: /srv/app/elasticsearch/plugins
>>> bootstrap.mlockall: True
>>> transport.tcp.port: 9300
>>> http.port: 9200
>>> http.enabled: True
>>> gateway.type: local
>>> gateway.recover_after_nodes: 1
>>> gateway.recover_after_time: 2m
>>> gateway.expected_nodes: 1
>>> discovery.zen.minimum_master_nodes: 1
>>> discovery.zen.ping.timeout: 30s
>>> discovery.zen.ping.multicast.enabled: False
>>> discovery.zen.ping.unicast.hosts: ["elastic1.internal.cluster.net", 
>>> "elastic2.internal.cluster.net", "elastic3.internal.cluster.net", 
>>> "elastic4.internal.cluster.net", "elastic5.internal.cluster.net"]
>>> action.auto_create_index: True
>>> action.disable_delete_all_indices: True
>>> script.disable_dynamic: False
>>> threadpool.bulk.type: fixed
>>> threadpool.bulk.size: 50
>>> threadpool.bulk.queue_size: 1000
>>> -- 
>>> 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 elasticsearc...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/elasticsearch/f724407f-6163-4433-9dd7-5c8c66fcece2%40googlegroups.com.
>>> For more options, visit 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/elasticsearch/44b06669-bb82-4275-acdf-e8fdabc95c06%40googlegroups.com.
> For more options, visit 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/145933F0-7704-4E6B-B389-1670B2625B86%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Re: ElasticsearchIllegalArgumentException can't parse config file

2015-01-26 Thread Xavier Garcia 
Already try but doesn't work.

Le lundi 26 janvier 2015 14:08:39 UTC-8, David Pilato a écrit :
>
> Could you try replacing True by true?
>
> David
>
> Le 26 janv. 2015 à 22:49, Xavier Garcia > a 
> écrit :
>
> Hello guy,
>
> I'm configuring a ES cluster and i got this issue - 
> *ElasticsearchIllegalArgumentException[value 
> cannot be parsed to boolean [ true/1/on/yes OR false/0/off/no ]  ]*
> I try to increase the level of logging but nothing work i can't find the 
> right line, do you have any idea where is this value in my config file ?
>
> Thank you
>
>
> cluster.name: Cluster-Production
> node.name: elastic2.cluster.net
> node.master: True
> node.rack: ec2
> node.max_local_storage_nodes: 1
> node.data: /srv/data/elasticsearch
> index.mapper_dynamic: True
> index.query.bool.max_clause_count: 4096
> path.conf: /srv/conf/elasticsearch
> path.data: /srv/data/elasticsearch
> path.logs: /srv/logs/elasticsearch
> path.plugins: /srv/app/elasticsearch/plugins
> bootstrap.mlockall: True
> transport.tcp.port: 9300
> http.port: 9200
> http.enabled: True
> gateway.type: local
> gateway.recover_after_nodes: 1
> gateway.recover_after_time: 2m
> gateway.expected_nodes: 1
> discovery.zen.minimum_master_nodes: 1
> discovery.zen.ping.timeout: 30s
> discovery.zen.ping.multicast.enabled: False
> discovery.zen.ping.unicast.hosts: ["elastic1.internal.cluster.net", "
> elastic2.internal.cluster.net", "elastic3.internal.cluster.net", "
> elastic4.internal.cluster.net", "elastic5.internal.cluster.net"]
> action.auto_create_index: True
> action.disable_delete_all_indices: True
> script.disable_dynamic: False
> threadpool.bulk.type: fixed
> threadpool.bulk.size: 50
> threadpool.bulk.queue_size: 1000
>
> -- 
> 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 elasticsearc...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/elasticsearch/f724407f-6163-4433-9dd7-5c8c66fcece2%40googlegroups.com
>  
> 
> .
> For more options, visit 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/44b06669-bb82-4275-acdf-e8fdabc95c06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ElasticsearchIllegalArgumentException can't parse config file

2015-01-26 Thread David Pilato 
Could you try replacing True by true?

David

> Le 26 janv. 2015 à 22:49, Xavier Garcia  a écrit :
> 
> Hello guy,
> 
> I'm configuring a ES cluster and i got this issue - 
> ElasticsearchIllegalArgumentException[value cannot be parsed to boolean [ 
> true/1/on/yes OR false/0/off/no ]  ]
> I try to increase the level of logging but nothing work i can't find the 
> right line, do you have any idea where is this value in my config file ?
> 
> Thank you
> 
> 
> cluster.name: Cluster-Production
> node.name: elastic2.cluster.net
> node.master: True
> node.rack: ec2
> node.max_local_storage_nodes: 1
> node.data: /srv/data/elasticsearch
> index.mapper_dynamic: True
> index.query.bool.max_clause_count: 4096
> path.conf: /srv/conf/elasticsearch
> path.data: /srv/data/elasticsearch
> path.logs: /srv/logs/elasticsearch
> path.plugins: /srv/app/elasticsearch/plugins
> bootstrap.mlockall: True
> transport.tcp.port: 9300
> http.port: 9200
> http.enabled: True
> gateway.type: local
> gateway.recover_after_nodes: 1
> gateway.recover_after_time: 2m
> gateway.expected_nodes: 1
> discovery.zen.minimum_master_nodes: 1
> discovery.zen.ping.timeout: 30s
> discovery.zen.ping.multicast.enabled: False
> discovery.zen.ping.unicast.hosts: ["elastic1.internal.cluster.net", 
> "elastic2.internal.cluster.net", "elastic3.internal.cluster.net", 
> "elastic4.internal.cluster.net", "elastic5.internal.cluster.net"]
> action.auto_create_index: True
> action.disable_delete_all_indices: True
> script.disable_dynamic: False
> threadpool.bulk.type: fixed
> threadpool.bulk.size: 50
> threadpool.bulk.queue_size: 1000
> -- 
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/elasticsearch/f724407f-6163-4433-9dd7-5c8c66fcece2%40googlegroups.com.
> For more options, visit 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/3D4610A7-D015-4104-9155-DC93C2F0B14C%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.