On 4/5/2022 12:38 PM, gnandre wrote:
I conducted the test that you mentioned.
Here is the diff - https://www.diffchecker.com/sdsMiGW5
Left hand side is the state before the in-place update. Right hand side is
the state after the in-place update.
That looks very strange to me. If it were doing a full add/delete type
of atomic update, I would expect there to be a new segment, but that
shows all the same segments and new timestamps on the files for the oyyo
segment, with the fdt file (which I believe has stored field data)
changing size. Not what I thought would happen for EITHER scenario.
But I have to admit that I am not completely sure how things happen at
the Lucene level for in-place updates.
These listings shows the user and group for those files as 8983 ... so
the OS where you gathered this info is NOT the system where Solr is
actually running. It could be either a container situation like Docker,
or a network filesystem. I believe that uid/gid 8983 is used for the
solr user in the docker images available for solr.
Thanks,
Shawn
