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
Service fails to restart on ubuntu-trusty-14.04-amd64-server-20160314 #53
Comments
I investigated this bug recently. On some virtual machines, ClickHouse think, that there are zero number of CPU cores. Reason could be a bug in cpuid library or incorrect result of virtualized 'cpuid' instruction. Right now you could build master revision from sources. |
In release. |
Thanks! |
I'm trying to install Clickhouse on AWS. Initially I decided to use instance-store for better IO performance and the AMI for instances that supports instance-store is
ubuntu-trusty-14.04-amd64-server-20160314.manifest.xml (ami-2c717046)
.I simply install Clickhouse from
http://repo.yandex.ru/clickhouse/trusty stable main
, start ClickHouse service and runclickhouse-client
. Then I create a table like this one: (the table definition doesn't make difference)CREATE TABLE testtable ( EventDate Date, UserID UInt64, Attrs Nested( Key String, Value String) ) ENGINE = MergeTree(EventDate, UserID, 8192)
Then I restarted clickhouse-server service but clickhouse-client was not able to connect the server. Unfortunately clickhouse-server doesn't log any error message (clickhouse.err, stderr and stdout is empty) but output of clickhouse.log file is similar to this one:
It seems that the server got stuck when loading the table and never able to start.
service clickhouse-server stop
also got stuck since the process doesn't respond so I had to execute forcestop command in order to shutdown the clickhouse-server process.If I don't create any table, I'm able to restart the service without any issue. Also when I try to install Clickhouse on
ubuntu/images/hvm-ssd/ubuntu-trusty-14.04-amd64-server-20160114.5 (ami-fce3c696)
it works as expected.The text was updated successfully, but these errors were encountered: