If I want to use the techpreview elasticsearch5 images are there any other
changes I need to make as I am seeing this on startup:
Found index level settings on node level configuration.
Since elasticsearch 5.x index level settings can NOT be set on the nodes
configuration like the elasticsea
On 3/21/19 1:23 PM, Neale Ferguson wrote:
If I want to use the techpreview elasticsearch5 images are there any other
changes I need to make as I am seeing this on startup:
Found index level settings on node level configuration.
Since elasticsearch 5.x index level settings can NOT be set on th
On 3/21/19, 15:33, "Neale Ferguson" wrote:
Right. The image is now
https://hub.docker.com/r/openshift/origin-logging-elasticsearch5/tags - there
are similar changes for origin-logging-curator5, origin-logging-kibana5,
origin-logging-fluentd
What version of o
On 3/21/19 1:33 PM, Neale Ferguson wrote:
On 3/21/19, 15:33, "Neale Ferguson" wrote:
Right. The image is now
https://hub.docker.com/r/openshift/origin-logging-elasticsearch5/tags - there
are similar changes for origin-logging-curator5, origin-logging-kibana5,
origin-loggin
elasticsearch 5 is not tech preview in 3.11 - it is fully supported - and
2.x is gone
- Understood. Did that change with the move from 3.10 to 3.11? I must've been
scanning another host which was running 3.10 to spot those preview vars.
- So this leads to the question of how to debug the ela
On 3/21/19 1:41 PM, Neale Ferguson wrote:
elasticsearch 5 is not tech preview in 3.11 - it is fully supported - and
2.x is gone
- Understood. Did that change with the move from 3.10 to 3.11?
Yes
I must've been scanning another host which was running 3.10 to spot those
preview vars.
-
> - So this leads to the question of how to debug the elasticsearch
container not coming up. The console log information in the 1st email came from
me running it manually so I could add the -v option to the elasticsearch
command. Setting the DEBUG and LOGLEVEL environment variables wasn't
On 3/21/19 1:56 PM, Neale Ferguson wrote:
> - So this leads to the question of how to debug the elasticsearch
container not coming up. The console log information in the 1st email came from me
running it manually so I could add the -v option to the elasticsearch command.
Setting the DEBU
Are you asking how to erase everything and start over?
- No, just how to get information out of the elasticsearch container to tell me
why it's failing.
Can you share your inventory files with the logging parameters (be sure to
redact any sensitive information)?
- The configuration
On 3/21/19 2:31 PM, Neale Ferguson wrote:
Are you asking how to erase everything and start over?
- No, just how to get information out of the elasticsearch container to tell me
why it's failing.
Can you share your inventory files with the logging parameters (be sure to redact any
Thanks anyway. I'll take a deeper look into what's happening inside the
container when it's started.
I think I should add an infra node rather than tie up the master as the logging
stuff looks a little heavy on resources. I've had a couple of instances where
when logging is brought up the api c
On 3/21/19 4:10 PM, Neale Ferguson wrote:
Thanks anyway. I'll take a deeper look into what's happening inside the
container when it's started.
I think I should add an infra node rather than tie up the master as the logging
stuff looks a little heavy on resources.
Yes. We use a minimum memo
12 matches
Mail list logo