-
Notifications
You must be signed in to change notification settings - Fork 4
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
HDFS with one NameNode and no JournalNodes (no HA) for Integration Tests #266
Comments
It is a great idea but I'm not sure if our HDFS even supports a non-HA setup. |
As far as i remember:
Ill run a quick test today. |
Running with nightly: I removed the check here hdfs-operator/rust/crd/src/lib.rs Line 507 in ecacb76
But the namenode is not coming up. So this would require more investigation. |
Yes, it requires a different configuration if running without HA. |
Yeah but it could significantly lower the test duration / resources if we can strip it down. Or switch to S3? |
We should either support it or if we don't support it then we shouldn't allow invalid configurations... |
Yeah, i was more talking about optimizing the tests. I think we could switch to minio for deep storage in most cases? |
At least for druid we could, yes. |
Ok did not see this is the hdfs-operator repo...the deep storage stuff pointed me to druid.. :D |
Druid uses HDFS for DeepStorage in its unit tests. A new HDFS instance needs to be spun up every time a test is run, and HDFS is a major contributor to the overall test duration, and also causes tests to fail occasionally because of its long startup times.
As I have learned today (thanks to Lars!), HDFS only uses a second NameNode and the JournalNodes for high availability (HA) but can also run without them. I think it would be great to have this. For an intance that only lives a few minutes and might not even see data written to it, the most bare-bones setup should be used.
The text was updated successfully, but these errors were encountered: