[ 
http://opencast.jira.com/browse/MH-8615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29563#comment-29563
 ] 

Jonathan Felder commented on MH-8615:
-------------------------------------

We don't want to keep copies indefinitely, probably just for the semester.  Of 
course we have considered the ramifications of running out of diskspace for 
recordings.  The idea would be for the capture agents to have enough storage to 
hold a semester's worth of recordings.  Furthermore consider this is a managed 
environment.  Each capture agent will be monitored via snmp for load, 
diskspace, etc.  The capture agent would not be the primary storage location 
for the recordings.  

I feel as though you are attempting to frame the discussion such that our use 
case is a terrible idea from an operational standpoint, when in fact it isn't 
except for the fact that there are all of these status updates.  In effect, the 
capture agents represent "free" storage that serve as excellent secondary 
backups.  

As for the logs, yes I'm running on debug but that isn't issue either.  The 
logs I'm referring to are the apache logs on the server which are logging all 
of the http requests, because apache is being used as a proxy for matterhorn.  
While an annoyance, this is more to illustrate the shear number of requests 
being made.  As I mentioned in the ticket, these updates represent potentially 
significant amounts of bandwidth with increasing numbers of agents and 
recordings.

What effects will modifying the state polling interval have?  For example if I 
switch that to once an hour or once a day, I presume this will also cause the 
server to not know what the capture agent is doing with an active recording, 
right?  Will this cause the server to indicate failure on the part of the 
capture agent to initiate the recording?  If that's the case, I would think 
changing this would be a bad idea.

What effects will modifying the capabilities interval have?  Does this also 
affect whether or not the server thinks the agent is online or idle?  If so, 
then changing this is probably also not a good idea.


                
> capture agent broadcasts the state every recording it has done every 10 
> seconds
> -------------------------------------------------------------------------------
>
>                 Key: MH-8615
>                 URL: http://opencast.jira.com/browse/MH-8615
>             Project: Matterhorn Project
>          Issue Type: Bug
>          Components: Capture (Devices and Software)
>    Affects Versions: 1.3, 1.2
>            Reporter: Jonathan Felder
>            Assignee: Adam McKenzie
>            Priority: Minor
>             Fix For: 1.4
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
http://opencast.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to