hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Hansen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-9616) libhdfs++ Add runtime hooks to allow a client application to add low level monitoring and tests.
Date Tue, 22 Mar 2016 15:50:25 GMT

     [ https://issues.apache.org/jira/browse/HDFS-9616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Bob Hansen updated HDFS-9616:
    Attachment: HDFS-9616.HDFS-8707.004.patch

New patch: fix spacing in event.h

To your question: since there is currently only one valid response for release builds, we
don't check the response at all.  As soon as we have actionable responses in release builds,
we'll revisit the call sites to Do The Right Thing.

> libhdfs++ Add runtime hooks to allow a client application to add low level monitoring
and tests.
> ------------------------------------------------------------------------------------------------
>                 Key: HDFS-9616
>                 URL: https://issues.apache.org/jira/browse/HDFS-9616
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs-client
>            Reporter: James Clampffer
>            Assignee: Bob Hansen
>         Attachments: HDFS-9616.HDFS-8707.002.patch, HDFS-9616.HDFS-8707.003.patch, HDFS-9616.HDFS-8707.004.patch
> It would be nice to have a set of callable objects and corresponding event hooks in useful
places that can be set by a client application at runtime.  
> This is intended to provide a scalable mechanism for implementing counters (#retries,
#namenode requests) or application specific testing e.g. simulate a dropped connection when
the test system running the client application requests.
> Current implementation plan is a struct full of callbacks (std::functions) owned by the
FileSystemImpl.  A callback could be set (or left as a no-op) and when the code hits the corresponding
event it will be invoked with a reference to the object (for context) and each method argument
by reference.  The callback returns a bool: true to continue execution or false to bail out
of the calling method.

This message was sent by Atlassian JIRA

View raw message