After watching the recording posted by Alexander for the June geode community meeting, I wondered if the cleanest thing to do is to ensure that "server2" (in the same pod with the Istio/Envoy sidecar that terminates) is also terminated.
I know that in our in-house testing, we use a sidecar with a preStop hook to pull back the logs each time a server or locator terminates. The side car gets a SIGTERM when the server or locator is shutdown and we're able to pull back our logs before the server or locator completes its shutdown. This made me wonder if perhaps this could be done the other way ... when the sidecar gets a termination signal, can it do something to shutdown the server in that same pod? I found this slide deck online which discusses a workaround for Istio/Envoy sidecars with postStart and preStop hooks for the sidecar and the app, so it seems that this is something that may be configurable (see pages 16-19). https://events.istio.io/istiocon-2021/slides/g6a-LongWildRiver-RaphaelFraysse.pdfPerhaps something like this could be used to force "server2" to exit when the sidecar is terminated. -l- ________________________________ From: Alexander Murmann <amurm...@vmware.com> Sent: Wednesday, June 2, 2021 11:52 AM To: dev@geode.apache.org <dev@geode.apache.org> Subject: Re: June Community Meeting Hi everyone! The wiki page<https://cwiki.apache.org/confluence/display/GEODE/Apache+Geode+Community+Meeting+Notes> now is updated with a very short summary of our meeting today and a link to the recording. Thanks to everyone who attended and especially Petar Tomic for presenting! ________________________________ From: Alberto Gomez <alberto.go...@est.tech> Sent: Monday, May 31, 2021 07:07 To: dev@geode.apache.org <dev@geode.apache.org> Subject: Re: June Community Meeting Hi all, Just a short note to inform you that we have added some more information in the Wiki page about the topic we plan to present in the meeting: * Title: "Servers waiting indefinitely for a reply" * Summary: If a packet is lost between servers, multiple threads get stuck and servers wait indefinitely for a reply, without any retry mechanism or timeout. * Context: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3Dlist%253Aorg.apache.geode.dev%2Border%253Adate-backward%23query%3Alist%253Aorg.apache.geode.dev%2520order%253Adate-backward%2Bpage%3A1%2Bmid%3Al6uw5vs62vmtcxo4%2Bstate%3Aresults&data=04%7C01%7Clhughes%40vmware.com%7C2a2ef0f384724ca24df408d925f7949b%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637582567562979984%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Ut4twLonYCeKze%2BZD80yoCvtnSP2KuBrL2Fu7lXzIiA%3D&reserved=0 Best regards, Alberto ________________________________ From: Alexander Murmann <amurm...@vmware.com> Sent: Wednesday, May 26, 2021 11:55 PM To: geode <dev@geode.apache.org> Subject: June Community Meeting Hi everyone, Next Wednesday, June 2nd, it's time for our next Geode Community Meeting. So far, our only agenda item is "geode retry/acknowledge improvement" presented by contributors from the team at Ericsson. If you have anything you'd like to present or discuss, please add it to our agenda on the project Confluence<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FGEODE%2FApache%2BGeode%2BCommunity%2BMeeting%2BNotes&data=04%7C01%7Clhughes%40vmware.com%7C2a2ef0f384724ca24df408d925f7949b%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637582567562979984%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=6r0KcyEu%2FImHecamMAnAJBIHmuL6uEzgPymCF%2B9XCgA%3D&reserved=0>. The same page also contains information on how to join. Looking forward to seeing you all there!
