Sort-last causing network problem

2 messages Options
Embed this post
Permalink
elwin

Sort-last causing network problem

Reply Threaded More More options
Print post
Permalink
Hi...

When I used the configuration 2-node.DB.ds.eqc, it is causing the following message in /var/log/messages.

Jun  3 14:55:38 n23 kernel: NETDEV WATCHDOG: eth0: transmit timed out

This is causing the rendering to "hang".

However, if I moved the inputframe { name "stripe1.c2" } into the previous compound as shown in the following, everything is fine.

compound
{
  range [ .5 1 ]
  outputframe { name "stripe2.c1" viewport [ 0 .5 1 .5 ] }
  inputframe { name "stripe1.c2" }
}

Any thoughts? Thanks.

BTW, I always see the following message. Is this ok? Or something wrong with my compilation?

21387 1094728032 ./lib/net/connectionSet.cpp:327 Cannot select connection RefPtr
<Connection 0x2a95b22c40 type N2eq3net16SocketConnectionE state closed descripti
on TCPIP#0##39#10000#172.20.0.22#35377#>, connection N2eq3net16SocketConnectionE
 does not use a file descriptor

Elwin
Stefan Eilemann

Re: [eq-dev] Sort-last causing network problem

Reply Threaded More More options
Print post
Permalink

On 3. Jun 2009, at 9:49, elwin (via Nabble) wrote:

> However, if I moved the inputframe { name "stripe1.c2" } into the  
> previous compound as shown in the following, everything is fine.

That should not change anything. My guess is you've hit bug 2796444:  
Race during simultaneous node connect. We're working on it.


> BTW, I always see the following message. Is this ok? Or something  
> wrong with my compilation?

That alone should be ok, but it points in the direction of the  
aforementioned bug.


Btw, direct-send on two nodes is slower than ordinary DB. If  
acceptable, I would recommend DB.stream for performance reasons.


Best,

Stefan.