-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Unable to Connect to HDFS for Tiered Storage Setup #63941
Comments
HDFS is unusable as a MergeTree disk with the current Clickhouse implementation |
Hey @den-crane, After reviewing the mentioned issue, it seems ClickHouse doesn't support HDFS. Is it possible to use a mounted or external disk for 'cold' storage instead? Any references or documentation on this would be greatly appreciated. |
right.
HDFS as an mounted/external disk? Never heard about such technology, I doubt it will work. |
Hey @den-crane No not HDFS as mounted disk. Thank you! |
Yes, you can. |
Hey @den-crane, I'm trying to use an external disk mounted to the ClickHouse server machine for cold storage, but I'm encountering the following error:
I have verified that the specified path Additional Information:
Could you please advise on the best approach to resolve this issue? Is downgrading ClickHouse a viable solution, or is there another recommended method to address this permission error? Thank you! |
|
Issue: Unable to Connect to HDFS for Tiered Storage Setup
Description
I am trying to implement a tiered storage setup using ClickHouse's External Storage with HDFS. I have configured the
storage_config.xml
in/etc/clickhouse/config.d/
as follows:Upon saving this configuration and restarting the ClickHouse server, I encounter the following error:
Additional Information:
$HADOOP_HOME/bin/hdfs fs -ls /
, which successfully lists the directories in the HDFS root directory.storage_config.xml
matches the one provided in thecore-site.xml
of the HDFS configuration.Questions
Steps to Reproduce
storage_config.xml
as shown above.Environment
Any guidance, reference documentation, or suggestions to resolve this issue would be greatly appreciated.
Thank you!
The text was updated successfully, but these errors were encountered: