-
Notifications
You must be signed in to change notification settings - Fork 25.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect date formatting in License Expiration logs #39136
Comments
Pinging @elastic/es-security |
Relates: #27330 @spinscale @rjernst
Do either of you know of a good solution for point 2? The options seem to be:
|
This format is handled different under java-time compared to joda-time Resolves: elastic#39136
@tvernum I think you are right - the jdk since 9 is using CLDR which is not specifying full format for ROOT locale. https://openjdk.java.net/jeps/252 I would rather prefer to break the behaviour in 7 and have a 'short form' names. But still using MMMM - I am not sure if we should expect at some point CLDR returning 'full form' for root locale? |
Due to migration from joda to java.time licence expiration 'full date' format has to use 4-char pattern (MMMM). Also since jdk9 the date with ROOT locale will still return abbreviated days and month names. closes #39136
Due to migration from joda to java.time licence expiration 'full date' format has to use 4-char pattern (MMMM). Also since jdk9 the date with ROOT locale will still return abbreviated days and month names. closes elastic#39136
Due to migration from joda to java.time licence expiration 'full date' format has to use 4-char pattern (MMMM). Also since jdk9 the date with ROOT locale will still return abbreviated days and month names. closes elastic#39136
@tsullivan I have changed this, but I noticed that by default we do run elasticsearch with |
Describe the feature:
Elasticsearch version (
bin/elasticsearch --version
):8.0.0-SNAPSHOT
Plugins installed: []
JVM version (
java -version
):OS version (
uname -a
if on a Unix-like system):Docker
Description of the problem including expected versus actual behavior:
Log message gives info on when my X-Pack license will expire, and the date string as formatted makes no sense. It reads: License [will expire] on [Sunday, 3 10, 2019]
elasticsearch_1 | {"type": "server", "timestamp": "2019-02-19T16:27:25,723+0000", "level": "WARN", "component": "o.e.l.LicenseService", "cluster.name": "dev-docker-cluster", "node.name": "73cce364f2b8", "cluster.uuid": "kNukTB2zQuW70QURs2g_dg", "node.id": "DjxjFDMjQ7WMbLrDsVxWmQ", "message": "License [will expire] on [Sunday, 3 10, 2019].\n# If you have a new license, please update it. Otherwise, please reach out to\n# your support contact.\n# \n# Commercial plugins operate with reduced functionality on license expiration:\n# - security\n# - Cluster health, cluster stats and indices stats operations are blocked\n# - All data operations (read and write) continue to work\n# - watcher\n# - PUT / GET watch APIs are disabled, DELETE watch API continues to work\n# - Watches execute and write to the history\n# - The actions of the watches don't execute\n# - monitoring\n# - The agent will stop collecting cluster and indices metrics\n# - The agent will stop automatically cleaning indices older than [xpack.monitoring.history.duration]\n# - graph\n# - Graph explore APIs are disabled\n# - ml\n# - Machine learning APIs are disabled\n# - logstash\n# - Logstash will continue to poll centrally-managed pipelines\n# - beats\n# - Beats will continue to poll centrally-managed configuration\n# - deprecation\n# - Deprecation APIs are disabled\n# - upgrade\n# - Upgrade API is disabled\n# - sql\n# - SQL support is disabled\n# - rollup\n# - Creating and Starting rollup jobs will no longer be allowed.\n# - Stopping/Deleting existing jobs, RollupCaps API and RollupSearch continue to function." }
Provide logs (if relevant):
The text was updated successfully, but these errors were encountered: