Lukas,
15 seconds is a substantial performance hit. I don't have a direct
answer to your question, but I wonder how these two machines are
networked--do they share a subnet? Are you using a 1Gbps Ethernet?
With only two machines, I would also experiment with a crossover cable.
> -----Original Message-----
> From: Lukas Pecha [mailto:pecha@stripped]
> Sent: Friday, June 26, 2009 7:35 AM
> To: cluster@stripped
> Subject: Question about communication between mysqld and ndbd
>
> Hi,
> I set up a small mysql-cluster configuration with two ndbd/API
machines
> - so there is ndbd and mysqld running on both of them. But I am not
able to find a
> way how to change a way the mysqld process communicates with ndbd - it
seems,
> that the machines are sending request to remote ndbd (not local), so
even not much
> complex queries take a long time (one simple query with "order by"
statement takes
> about 15 second and the table has only about twenty thousand rows).
When I kill one
> of the ndbd processes, the query takes only 0,2 sec on the machine
with both ndbd
> and mysqld running and still 15 seconds on the other machine. When I
start it up again,
> both machines have again the response time about 15 seconds.
>
> So my question is - is there a way, how to tell mysqld, that it should
use only local ndb
> daemon for querying? Or will this issue be resolved, if I start using
indexing
> everywhere I could?
>
> Thanks in advance
> Lukas Pecha