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
Running the test with following options:
Number of threads: 1
Report intermediate results every 1 second(s)
Initializing random number generator from current time
Initializing worker threads...
FATAL: Worker threads failed to initialize within 30 seconds!
root@sysbench:/#
`
No matter how many threads I set, it always fails. The pod is in the same namespace as mysql.
I am connecting to the mysql service, which is type Load Balancer.
$ kubectl get svc -n mysql-innodbcluster NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) mysql-innodbcluster LoadBalancer 10.43.87.246 192.168.10.240 3306:31495/TCP,33060:31435/TCP,6446:32361/TCP,6448:32111/TCP,6447:31948/TCP,6449:32073/TCP,8443:31111/TCP
Online I found other few posts of people who got the same error and it was told them that the issue arises when the sysbench pod is trying to connect to mysql via TCP. This sounds no sense to me, as how is the sysbench pod supposed to connect to another pod, if not via TCP?
Is there any solution to this issue or it i snot possible to use sysbench to perf test mysql in containerised environment?
Thanks in advance.
The text was updated successfully, but these errors were encountered:
Hello,
I have a pod created for sysbench and when I try to initialize it to connect to mysql I get the following:
`root@sysbench:/# sysbench oltp_read_only --tables=10 --table_size=100 --mysql-host=mysql-innodbcluster --mysql-port=31495 --mysql-user=root --mysql-password=testpasswd --mysql-db=testdb --time=300 --threads=1 --report-interval=1 run
sysbench 1.0.17 (using bundled LuaJIT 2.1.0-beta2)
Running the test with following options:
Number of threads: 1
Report intermediate results every 1 second(s)
Initializing random number generator from current time
Initializing worker threads...
FATAL: Worker threads failed to initialize within 30 seconds!
root@sysbench:/#
`
No matter how many threads I set, it always fails. The pod is in the same namespace as mysql.
I am connecting to the mysql service, which is type Load Balancer.
$ kubectl get svc -n mysql-innodbcluster NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) mysql-innodbcluster LoadBalancer 10.43.87.246 192.168.10.240 3306:31495/TCP,33060:31435/TCP,6446:32361/TCP,6448:32111/TCP,6447:31948/TCP,6449:32073/TCP,8443:31111/TCP
Online I found other few posts of people who got the same error and it was told them that the issue arises when the sysbench pod is trying to connect to mysql via TCP. This sounds no sense to me, as how is the sysbench pod supposed to connect to another pod, if not via TCP?
Is there any solution to this issue or it i snot possible to use sysbench to perf test mysql in containerised environment?
Thanks in advance.
The text was updated successfully, but these errors were encountered: