ES translogs & best practices


(pmanvi) #1

We are evaluating option to keep the translogs in either RAMDISK or the
SSDs.

  1. Is there any way we can specify the translog to dedicated directory (I
    couldn't find any...)

We have 100s of indexes that get generated, so its difficult to if we use
RAM disk option mount to a directory (mount -t ramfs ram /mnt/ram)
/data/..//nodes/0/indices//0/index/
a job to create symlinks to each newly created directory & copying to mount
could be one option...

  1. . Does anyone has done so & measured the impact?.
    Most of the data that we measured translogs are in MBs,
  2. Value for index.translog.flush_threshold
    We don;t have stringent requirement for real time updates (we were OK with
    delay in the order of minutes to available for search), with that
    background what is the better value to use.(default is 5000) , with 10000
    we did not see any noticeable change with ingesting about ~20GB of data.
    (Indexing time or timeouts)

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/ec3f69c2-94ca-4437-a1ba-7a68df565ab7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(system) #2