[mythtv-commits] Ticket #4254: Wrong backend selected to stream LiveTV
MythTV
mythtv at cvs.mythtv.org
Sun Dec 2 01:03:14 UTC 2007
#4254: Wrong backend selected to stream LiveTV
--------------------+-------------------------------------------------------
Reporter: keller | Owner: ijr
Type: defect | Status: new
Priority: minor | Milestone: unknown
Component: mythtv | Version: head
Severity: medium | Mlocked: 0
--------------------+-------------------------------------------------------
Here's the situation. Please tell me if my logic is wrong on this. This
is all running almost-newest SVN.
Two backends:
Master - RAID 5 Storage. Default and LiveTV Storage Groups point to the
local directories. Both directories are shared via NFS.
Slave - Tuners, no local storage. Master shares mounted via NFS. Default
and LiveTV Storage Groups point to the NFS mounts.
Master Backend Override is on. ALL file reads should come from the
Master.
My frontend is connected to the master backend. When I go to watch
LiveTV, the slave begins recording to the correct directory (NFS share
that points to Master). The frontend, however, begins streaming from the
slave backend. The file is available on the Master backend, but it
streams from the slave instead. This causes triple TV traffic on the
network:
One trip from slave to master storage via NFS
Second trip from master storage to slave via NFS
Third trip from slave to frontend via mythtv protocol
If Master Backend Override is enabled, shouldn't the master backend check
to see if the LiveTV file is local, and then stream it to the frontend?
Also note that once the program is not being recorded, it can be streamed
from the Master backend correctly. This also goes for previously-recorded
programs. It's JUST LiveTV that displays this behavior.
Please let me know if my logic is off. If this should be a patch, let me
know and I'll see what I can cook up.
-Keller
--
Ticket URL: <http://svn.mythtv.org/trac/ticket/4254>
MythTV <http://svn.mythtv.org/trac>
MythTV
More information about the mythtv-commits
mailing list