[mythtv-commits] Ticket #7847: After resume from long S3 sleep, scheduling via EPG isn't refreshed on EPG

[MythTV]

#7847: After resume from long S3 sleep, scheduling via EPG isn't refreshed on EPG
------------------------------+---------------------------------------------
 Reporter:  warpme@…          |       Owner:  ijr           
     Type:  defect            |      Status:  infoneeded_new
 Priority:  minor             |   Milestone:  0.23          
Component:  MythTV - General  |     Version:  0.22-fixes    
 Severity:  medium            |     Mlocked:  0             
------------------------------+---------------------------------------------

Comment(by warpme@…):

 Hi,

 Thx for quick response.[[BR]]


 I applied this patch for testing purposes.  Tested on 0.22-fixes 23426 +
 ticket 7836[[BR]]


 Results:[[BR]]

 After resume from sleep, with sleep period longer than keep-alive-time
 +(keep-alive-intrval*keep-alive-probes), user sees dialog "backend
 connection lost".[[BR]]

 By this I would say changset 23397 is serious regression for setups with
 separated FE & BE and when user is using S3 on FE.[[BR]]


 I think it is expected result, as keep-alive is closing all TCP
 connections between BE-FE when sleep time is longer than keep-alive-time
 +(keep-alive-intrval*keep-alive-probes).[[BR]]

 From this perspective, 23397 is serious regression as it causes FE-BE
 connection loss on sleeping FEs. In my case user sees "Backend connection
 lost" popup. When user trying still select recording to watch - FE crashes
 (this crash is not result of this patch. I have it also i.e. when I
 restart BE when FE sleeps).[[BR]]


 Anyway - I think scenario with separated BE and FE when FE are using S3
 for sleeps needs rethinking.[[BR]]
 I would consider i.e. using TCP connections for all conn. initiated from
 FE to BE, and for long, persistent connections initiated from BE to FE I
 would consider switch from TCP to UDP. As UDP is stateless - maybe it will
 help solve problem ?[[BR]]

 TCP Keep-alive solution is definitely bad idea IMHO and should be reverted
 form trunk.[[BR]]


 Regarding heart-beat approach - I think it will be not so easy, as we will
 need in BE a way discover FE in sleeping state.
 Without it, BE will falsely threat slipping FEs as dead FEs.[[BR]]

 Probably simpler approach will be approach with keeping all FE->BE
 connections as always-on, and changing persistent BE->FE connections to
 state-less type (UDP)[[BR]]


 br

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/7847#comment:4>
MythTV <http://www.mythtv.org/>
MythTV