You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After I installed kudu and run "service kudu-master start",then get the problem below.Anyone can help me.
IO error:
Could not create new FS layout:
Unable to create block manager: Error during hole punch test.
The log block manager requires a filesystem with hole punching support such as ext4 or xfs. On el6, kernel version 2.6.32-358 or newer is required.
To run without hole punching (at the cost of some efficiency and scalability), reconfigure Kudu with --block_manager=file.
Refer to the Kudu documentation for more details.
Raw error message follows: Unexpected post-punch file size for /var/lib/kudu/master/data/hole_punch_test_file: expected 8192 but got 16384
The text was updated successfully, but these errors were encountered:
I ran "kudu-master --block_manager=file" as the document recommended.But got another problem:Check failed: _s.ok() Bad status: IO error: Failed to load FS layout: Write-ahead log directory (fs_wal_dir) not provided.
so, I checked the configuration,and made a directory in /var/lib/kudu, and ran 'chmod 777 .',still reported the problem.
I'm glad that you've tried our Docker image and apologize for the current
lack of documentation on how to use the image.
There is actually 2 images in this repository:
kudu-src which is for people wishing to build Kudu from source.
Probably only useful for Kudu developers.
and impala-kudu which is for people wishing to try out Kudu with
Impala.
I am assuming what you want is #2, so please try the following:
cd impala-kudu-0.5/
docker build -t kudu .
docker run -ti kudu demo
The demo command will start all the services for you (see
docker-entrypoint.sh) and starts a bash shell. Once you exit the bash
shell, your Kudu container will also exit.
Please note that the "demo" behavior is likely to change on future updates
to this image. If you have ideas on how to improve it, please share them
with us.
I ran "kudu-master --block_manager=file" as the document recommended.But
got another problem:Check failed: _s.ok() Bad status: IO error: Failed to
load FS layout: Write-ahead log directory (fs_wal_dir) not provided.
so, I checked the configuration,and made a directory in /var/lib/kudu, and
ran 'chmod 777 .',still reported the problem.
—
Reply to this email directly or view it on GitHub #6 (comment)
.
After I installed kudu and run "service kudu-master start",then get the problem below.Anyone can help me.
IO error:
Could not create new FS layout:
Unable to create block manager: Error during hole punch test.
The log block manager requires a filesystem with hole punching support such as ext4 or xfs. On el6, kernel version 2.6.32-358 or newer is required.
To run without hole punching (at the cost of some efficiency and scalability), reconfigure Kudu with --block_manager=file.
Refer to the Kudu documentation for more details.
Raw error message follows: Unexpected post-punch file size for /var/lib/kudu/master/data/hole_punch_test_file: expected 8192 but got 16384
The text was updated successfully, but these errors were encountered: