BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//bbuzz22//speaker//3CMEKA
BEGIN:VTIMEZONE
TZID:Europe/Berlin
BEGIN:DAYLIGHT
DTSTART:20210614T000000
TZNAME:CEST
TZOFFSETFROM:+0200
TZOFFSETTO:+0200
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20211031T030000
RDATE:20221030T030000
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20220327T030000
RDATE:20230326T030000
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:Autoscaling Elasticsearch for Logs on Kubernetes - Radu Gheorghe\,
  Ciprian Hacman
DTSTART;TZID=Europe/Berlin:20220614T140000
DTEND;TZID=Europe/Berlin:20220614T144000
DTSTAMP:20261117T192926Z
UID:pretalx-bbuzz22-QJZPYZ@pretalx.com
DESCRIPTION:Elasticsearch (or OpenSearch) clusters likely need to scale to
  adapt to changes in load. But autoscaling Elasticsearch isn't trivial: in
 dices and shards need to be well sized and well balanced across nodes. Oth
 erwise the cluster will have hotspots and scaling it further will be less 
 and less efficient.\n\nThis talk focuses on two aspects:\n- best practices
  around scaling Elasticsearch for logs and other time-series data\n- how t
 o apply them when deploying Elasticsearch on Kubernetes. In the process\, 
 a new (open-source) operator will be introduced (yes\, there will be a dem
 o!). This operator will autoscale Elasticsearch while keeping a good balan
 ce of load. It does so by changing the number of shards in the index templ
 ate and rotating indices when the number of nodes changes.\n\nThe Search t
 rack is presented by OpenSource Connections
LOCATION:Frannz Salon
URL:https://pretalx.com/bbuzz22/talk/QJZPYZ/
END:VEVENT
END:VCALENDAR
