Thank you Uwe,
This is the answer I was looking for. A bit unfortunate this is happening but,
it is what it is. At least, when Google will index this discussion, this will
be available and informative for anyone attempting using the same solution.
Many thanks for your help and for your explanat
Hi,
Yeah, sorry for leading the issue into the wrong direction. I was just
stumbling on the exception message and because we do not spend much time
in improving/supporting the use of NIOFSDirectory, I may have moved this
mailing list thread into the wrong direction.
I don't think the directo
Hi Uwe,
I will report the bug to ES, as you suggested.
Do you recon using Mmap would have an effect to the index corruption when using
SMB? I have to report back to my manager in few days to decide wether to carry
on with ACIs or find another hosting solution. It is unfortunate there seems to
Hi,
Please open a bug report at ES. The setting vm.max_map_count is not
needed and should not be changed unless really needed, because it uses
kernel resources.
This has to do with their support (they try to tell people to overshard
and to prevent support requests they ask to raise this seet
I also tried enabling preview but no joy, same error :(
It looks like it is not possible to start a multinode ES cluster without
setting vm.max_map_count. I also googled it and this check cannot be disabled.
I guess MMapDirectory is not an option for ES on ACIs, unless you have
something else I
Hmm, I’m afraid I hit a roadblock:
2023-01-02T17:01:31,157][INFO ][o.e.b.BootstrapChecks]
[fs-sdlc-elasticsearch-001] bound or publishing to a non-loopback address,
enforcing bootstrap checks
bootstrap check failure [1] of [1]: max virtual memory areas vm.max_map_count
[65530] is too low, i
Thank you Uwe, this is great! I am rebuilding the cluster using MMapDirectory
and no enable-preview, as you suggested. Let’s see what happens.
Cheers,
Seb
> On 2 Jan 2023, at 17:51, Uwe Schindler wrote:
>
> Hi,
>
> in recent versions it works like that:
>
> https://www.elastic.co/guide/en/e
Hi,
in recent versions it works like that:
https://www.elastic.co/guide/en/elasticsearch/reference/current/advanced-configuration.html#set-jvm-options
So in folder jvm.options.d/ add a new file (like "preview.conf") and put
"19:--enable-preview" into it. It is basically the same like modifying
Hi Uwe,
Sorry for the late reply but upgrading the docker image to use OpenJDK was
easier said that done.
I am not a Java developer/expert so, sorry for the stupid question but, how do
I specify the --enable-preview flag? ES has got a quite complex way to start so
I cannot specify the flag on
Your files are getting truncated. Nothing lucene can do.
If this is really the only way you can store data in this azure cloud,
and this is how they treat it, then run away... don't just walk... to
a different cloud.
On Mon, Jan 2, 2023 at 5:19 AM S S wrote:
>
> We are experimenting with Elastic
Hi Uwe,
This sounds very interesting, I will try this configuration this afternoon and
I’ll let you know what happens.
Many thanks for the suggestion! :)
Seb
> On 2 Jan 2023, at 11:48, Uwe Schindler wrote:
>
> Hi,
>
> in general you can still use MMapDirectory. There is no requirement to
Hi,
in general you can still use MMapDirectory. There is no requirement to
set vm.max_map_count for smaller clusters. The information in Elastics
documentation is not mandatory and misleading.
If you use newest version of Elasticsearch with Java 19 and you use
`--enable-preview` in you jvm.p
12 matches
Mail list logo
