Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kubernetes deployment error: Could not initialize class alluxio.conf.PropertyKey #18585

Open
sadatnfs opened this issue Apr 21, 2024 · 5 comments
Labels
type-bug This issue is about a bug

Comments

@sadatnfs
Copy link

Alluxio Version:
2.9.3 and master branch

Describe the bug
Master process doesn't start with this error:
Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize class alluxio.conf.PropertyKey
at alluxio.ProcessUtils.fatalError(ProcessUtils.java:116)
at alluxio.master.AlluxioMaster.main(AlluxioMaster.java:47)

To Reproduce
Deploy master stateful set YAML on Kubernetes, or even deploy the Helm chart

I suspect there's some configuration or environment variable I'll need to set for my pods. Any help would be appreciated

@sadatnfs sadatnfs added the type-bug This issue is about a bug label Apr 21, 2024
@jasondrogba
Copy link
Contributor

I guess you did not set properties in values.yaml

# Site properties for all Alluxio components
properties:

@sadatnfs
Copy link
Author

I only set the ufs properties. Do you know which ones I gotta set for kubernetes?

@jasondrogba
Copy link
Contributor

How did you deploy the cluster? Did you obtain the Alluxio Docker image from official, or did you compile and build it yourself?

@sadatnfs
Copy link
Author

@jasondrogba i compiled Alluxio myself with Maven calls, because the existing binaries have CVEs that we can't use with work. And then put it in our Docker image

@jasondrogba
Copy link
Contributor

jasondrogba commented Apr 24, 2024

@sadatnfs It could be an issue generated by your compilation of Alluxio. Have you deployed and used it on a physical machine after compiling?
Because the error you reported doesn't seem to be caused by Docker, and it's rarely encountered, I suspect it might be a problem with your Maven compilation.
You could try compiling it and testing it on a machine to confirm if the issue persists. Alternatively, you could review if any changes have been made to the code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-bug This issue is about a bug
Projects
None yet
Development

No branches or pull requests

2 participants