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

Siddharth Wagle updated HDDS-5397:
----------------------------------
    Labels: newbie  (was: )

> Problems when running Ozone cluster from IDE
> --------------------------------------------
>
>                 Key: HDDS-5397
>                 URL: https://issues.apache.org/jira/browse/HDDS-5397
>             Project: Apache Ozone
>          Issue Type: Improvement
>            Reporter: Xiang Zhang
>            Priority: Minor
>              Labels: newbie
>
> I am trying to run ozone in IDEA again after 1 year. I am following 
> instructions here: 
> [https://cwiki.apache.org/confluence/display/OZONE/Run+Ozone+cluster+from+IDE.]
> Two problem came up.
>  # After importing configs by executing 
> `./hadoop-ozone/dev-support/intellij/install-runconfigs.sh`, the module names 
> become a little confusing. For CsiServer, the classpath is ozone, but the 
> project home directory is ozone and the module name for hadoop-ozone in IDEA 
> is ozone, so the latter become `ozone[1]`, which is fine, I edit the config 
> to let it use `ozone[1`], however it cannot start:
>  
> Error: Could not find or load main class org.apache.hadoop.ozone.csi.CsiServer
>  # When running StorageContainerManagerInit, following error occurred:
> java: cannot access 
> org.apache.hadoop.ozone.common.ChunkBufferImplWithByteBufferList$1
>  bad class file: 
> /Users/tanchenchi/workspace/source/ozone/hadoop-hdds/common/target/classes/org/apache/hadoop/ozone/common/ChunkBufferImplWithByteBufferList$1.class
>  bad enclosing method attribute for class 
> org.apache.hadoop.ozone.common.ChunkBufferImplWithByteBufferList$1
>  Please remove or make sure it appears in the correct subdirectory of the 
> classpath.
>  
> Please let me know it is just me or common for everyone.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to