Open OnePainter opened 2 months ago
byconity version 0.4.1
For analysis and troubleshooting, need the following information:
new problem when i insert data Received exception from server (version 21.8.7): Code: 1000. DB::Exception: Received from localhost:9010. DB::Exception: Access to file denied: Permission denied: user=clickhouse, access=WRITE, inode="/":root:supergroup:drwxr-xr-x at org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:506) at org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:346) at org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermissionWithContext(FSPermissionChecker.java:370) at org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:240) at org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1943) at org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1927) at org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkAncestorAccess(FSDirectory.java:1886) at org.apache.hadoop.hdfs.server.namenode.FSDirMkdirOp.mkdirs(FSDirMkdirOp.java:60) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.mkdirs(FSNamesystem.java:3438) at org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.mkdirs(NameNodeRpcServer.java:1166) at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.mkdirs(ClientNamenodeProtocolServerSideTranslatorPB.java:742) at org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java) at org.apache.hadoop.ipc.ProtobufRpcEngine2$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine2.java:621) at org.apache.hadoop.ipc.ProtobufRpcEngine2$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine2.java:589) at org.apache.hadoop.ipc.ProtobufRpcEngine2$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine2.java:573) at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1213) at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:1089) at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:1012) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:422) at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1899) at org.apache.hadoop.ipc.Server$Handler.run(Server.java:3026) SQLSTATE: HY000.
looks like some issue with HDFS write access. Did you install the HDFS yourself? did you run the script in the installation guide to create the users?
There is no handle /metrics
Use / or /ping for health checks. Or /replicas_status for more sophisticated health checks.
Send queries from your program with POST method or GET /?query=...
Use clickhouse-client:
For interactive data analysis: clickhouse-client
For batch query processing: clickhouse-client --query='SELECT 1' > result clickhouse-client < query > result
Code: 115, e.displayText() = DB::Exception: Setting match[] is neither a builtin setting nor started with the prefix 'SQL_' registered for user-defined settings SQLSTATE: 42000 (version 21.8.7.1)
global: scrape_interval: 15s # Set the scrape interval to every 15 seconds. Default is every 1 minute. evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute.
alerting: alertmanagers:
rule_files:
scrape_configs:
job=<job_name>
to any timeseries scraped from this config.job_name: "prometheus"
static_configs:
2024.06.17 21:27:10.824006 [ 333 ] {}
org.apache.hadoop.hdfs.server.blockmanagement.BlockPlacementPolicy: Not enough replicas was chosen. Reason: {NO_REQUIRED_STORAGE_TYPE=1}
Code: 159. DB::Exception: Received from localhost:9010. DB::Exception: Query 949e1ba9-2d15-4673-9587-e9c51b6f3574 receive data timeout, maybe you can increase settings max_execution_time. Debug info for source ExchangeSource: MultiPathReceiver[1_0_00]: Try pop receive collector for MultiPathReceiver[1_0_00] timeout at 2024-06-18 08:39:56: While executing ExchangeSource: MultiPathReceiver[1_0_0_0_10.64.1.188:8124] SQLSTATE: HY000.
Timeout exceeded while receiving data from server. Waited for 300 seconds, timeout is 300 seconds. Cancelling query.
fdb> status
WARNING: Long delay (Ctrl-C to interrupt)
Using cluster file `fdb_runtime/config/fdb.cluster'.
Unable to start default priority transaction after 5 seconds.
Unable to start batch priority transaction after 5 seconds.
Unable to retrieve all status information.
Configuration: Redundancy mode - double Storage engine - ssd-2 Coordinators - 3 Usable Regions - 1
Cluster: FoundationDB processes - 12 Zones - 3 Machines - 3 Memory availability - 8.0 GB per process on machine with least available Fault Tolerance - 1 machines Server time - 06/20/24 16:39:17
Data: Replication health - Healthy Moving data - 0.000 GB Sum of key-value sizes - 6 MB Disk space used - 641 MB
Operating space: Storage server - 0.0 GB free on most full server Log server - 0.0 GB free on most full server
Workload: Read rate - 4 Hz Write rate - 0 Hz Transactions started - 2 Hz Transactions committed - 0 Hz Conflict rate - 0 Hz Performance limited by process: Log server running out of space (approaching 100MB limit). Most limiting process: xxxxxxxx:4501
Backup and DR: Running backups - 0 Running DRs - 0
Client time: 06/20/24 16:39:09
2024.06.21 13:11:14.537606 [ 32111 ] {}
SELECT * FROM TEST LIMIT 100 SETTINGS enable_optimizer_fallback = 0
Query id: f811e6d1-2cec-45ec-a610-e9b303257361
0 rows in set. Elapsed: 0.095 sec.
Received exception from server (version 21.8.7): Code: 2007. DB::Exception: Received from localhost:9010. DB::Exception: send plan segment async failed error code : 2001 error worker : 10.64.1.101:8124 error text : [E2001][10.64.1.101:123456789]Code: 516, e.displayText() = DB::Exception: dbadmin: Authentication failed: password is incorrect or there is no user with such name SQLSTATE: HY000,
I installed the physical machine on three nodes according to the physical machine deployment guide (https://byconity.github.io/zh-cn/docs/deployment/package-deployment) on the official website. byconity-tso.service, byconity-server.service, byconity-resource-manager.service, and byconity-daemon-manager.service are installed on the same node. byconity-worker.service is installed on one node, and byconity-worker-write.service is installed on another node. However, the following exception occurs on both worker nodes:
2024.06.13 10:22:53.981851 [ 24632 ] {} ResourceReporterTask: void DB::ResourceManagement::ResourceReporterTask::run(): Code: 7114, e.displayText() = DB::Exception: The leader from election result not work well SQLSTATE: HY000, Stack trace (when copying this message, always include the lines below):