[ 
https://issues.apache.org/jira/browse/HDDS-2250?focusedWorklogId=323881&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-323881
 ]

ASF GitHub Bot logged work on HDDS-2250:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 05/Oct/19 06:13
            Start Date: 05/Oct/19 06:13
    Worklog Time Spent: 10m 
      Work Description: adoroszlai commented on issue #1597: HDDS-2250. 
Generated configs missing from ozone-filesystem-lib jars
URL: https://github.com/apache/hadoop/pull/1597#issuecomment-538620916
 
 
   Thanks @elek for help in finding the root cause.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 323881)
    Time Spent: 1h 10m  (was: 1h)

> Generated configs missing from ozone-filesystem-lib jars
> --------------------------------------------------------
>
>                 Key: HDDS-2250
>                 URL: https://issues.apache.org/jira/browse/HDDS-2250
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: build, Ozone Filesystem
>            Reporter: Attila Doroszlai
>            Assignee: Attila Doroszlai
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 0.5.0
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Hadoop 3.1 and 3.2 acceptance tests started failing with HDDS-1720, which 
> added a new, annotated configuration class.
> The [change itself|https://github.com/apache/hadoop/pull/1538/files] looks 
> fine.  The problem is that the packaging process for {{ozone-filesystem-lib}} 
> jars keeps only 1 or 2 {{ozone-default-generated.xml}} files.  With the new 
> config in place, client configs are missing, so Ratis client gets evicted 
> immediately due to {{scm.container.client.idle.threshold}} = 0.  This results 
> in NPE:
> {code:title=https://elek.github.io/ozone-ci-q4/pr/pr-hdds-1720-trunk-rd9ht/acceptance/summary.html#s1-s5-t1-k2-k2}
> Running command 'hdfs dfs -put /opt/hadoop/NOTICE.txt 
> o3fs://bucket1.vol1/ozone-14607
> ...
> -put: Fatal internal error
> java.lang.NullPointerException: client is null
>       at java.util.Objects.requireNonNull(Objects.java:228)
>       at 
> org.apache.hadoop.hdds.scm.XceiverClientRatis.getClient(XceiverClientRatis.java:208)
>       at 
> org.apache.hadoop.hdds.scm.XceiverClientRatis.sendRequestAsync(XceiverClientRatis.java:234)
>       at 
> org.apache.hadoop.hdds.scm.XceiverClientRatis.sendCommandAsync(XceiverClientRatis.java:332)
>       at 
> org.apache.hadoop.hdds.scm.storage.ContainerProtocolCalls.writeChunkAsync(ContainerProtocolCalls.java:310)
> ...
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to