reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Weimer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1458) Driver should be enabled to write status logs in addition to sending it to client
Date Fri, 17 Jun 2016 16:32:05 GMT

    [ https://issues.apache.org/jira/browse/REEF-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336403#comment-15336403
] 

Markus Weimer commented on REEF-1458:
-------------------------------------

We should consider making this more broadly useful. There can be an object representing this
status. Whenever it is updated, it triggers an event, which we then can use to write to a
log or trigger other things. On the Java side, we have the class {{org.apache.reef.runtime.common.driver.client.ClientConnection}}
which represents the connection to a client to receive those messages. IIRC, there is some
infrastructure akin to what I am suggesting above which uses that class.

> Driver should be enabled to write status logs in addition to sending it to client
> ---------------------------------------------------------------------------------
>
>                 Key: REEF-1458
>                 URL: https://issues.apache.org/jira/browse/REEF-1458
>             Project: REEF
>          Issue Type: Sub-task
>          Components: REEF Driver, REEF.NET Client, REEF.NET Driver
>         Environment: C#
>            Reporter: Dhruv Mahajan
>
> Currently, HTTP endpoint is the only way for driver to send status to clients. However,
there might be scenarios where this endpoint mechanism might not be feasible. In that case
it would be desirable for the driver to write a log file to some remote/local location periodically.
This will require changes in driver (REEF.Net and Java). The aim of this JIRA is to come up
with a design and implement it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message