Hi,
I am getting this error:
Schema error: extra keys not allowed @ data['client']['timoeut']
the timeout is spelled as aboved.
Can advise?
thanks
Hi,
I am getting this error:
Schema error: extra keys not allowed @ data['client']['timoeut']
the timeout is spelled as aboved.
Can advise?
thanks
@ data['client']['timoeut'] is wrongly spelled, this should be @ data['client']['timeout']
But I dont know if that fixes your problem..
Hi @Kok_Sin_See,
This error usually occur if there is something wrong in your action file.
could you please share the action file with full logs for further investigation.
Regards,
Harsh Bajaj
Hi,
I tested the same configuration on my centos locally, it works.. The issue is when I tested in RHEL 7.2 production env. It was the same configuration file on both env.
How do I enable logging to a file?
thanks
Hi,
The timoeut - is generated by the curator itself. Not by my configuration. As a matter of fact, there is no such setting in the config file.
Any idea?
thanks
Hi,
You can find the docs on curator logging and configuration here.
This error is in the client configuration, not the action file. It implies an incorrect spelling of the timeout
key:
---
client:
# ... other stuff here
timeout: 30
logging:
# ... other stuff here.
In your case, the timeout
must be misspelled as timoeut
, resulting in the error.
Hi,
U r correct.. Already made the changes..
thanks
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
© 2020. All Rights Reserved - Elasticsearch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.