[
https://issues.apache.org/jira/browse/HDDS-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648598#comment-16648598
]
Hudson commented on HDDS-445:
-----------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15201 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/15201/])
HDDS-445. Create a logger to print out all of the incoming requests.
(aengineer: rev 3c1fe073d2fef76676660144e7dce2050761ae64)
* (edit) hadoop-ozone/dist/src/main/compose/ozones3/docker-config
* (edit) hadoop-common-project/hadoop-common/src/main/conf/log4j.properties
> Create a logger to print out all of the incoming requests
> ---------------------------------------------------------
>
> Key: HDDS-445
> URL: https://issues.apache.org/jira/browse/HDDS-445
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Elek, Marton
> Assignee: Bharat Viswanadham
> Priority: Major
> Fix For: 0.3.0, 0.4.0
>
> Attachments: HDDS-445.00.patch, HDDS-445.01.patch, HDDS-445.02.patch
>
>
> For the Http servier of HDDS-444 we need an option to print out all the
> HttpRequests (header + body).
> To create a 100% s3 compatible interface, we need to test it with multiple
> external tools (such as s3cli). While mitmproxy is always our best friend, to
> make it more easier to identify the problems we need a method to log all the
> incoming requests with a logger which could be turned on.
> Most probably we already have such kind of filter in hadoop/jetty the only
> thing what we need is to configure it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
