Roxie response slow, lot's of errors in log
Dear big guys,
Today we found roxie response is very slow, and a slave node is down, so we checked roxie.log and found lot's of errors about "Roxie slave received request for unregistered query".
Is it caused by code bug, or incorrect cluster configuration, lease give some ideas on how to read and fix it, thanks.
Roxie log is attached, I just keep the log tail because of upload size limitation.
BR,
Kevin
Today we found roxie response is very slow, and a slave node is down, so we checked roxie.log and found lot's of errors about "Roxie slave received request for unregistered query".
Is it caused by code bug, or incorrect cluster configuration, lease give some ideas on how to read and fix it, thanks.
Roxie log is attached, I just keep the log tail because of upload size limitation.
BR,
Kevin
- Attachments
-
roxie.7z
- roxie slave log
- (170.62 KiB) Downloaded 571 times
- kevinLv
- Posts: 11
- Joined: Thu Aug 15, 2013 3:20 am
The [unregistered query] error is usually caused when the Roxie is getting a new data package deployment.
I think its related to some nodes having Roxie up and responding to requests while other nodes are not yet responding. When we first started using OSS some people were running the "for" loop to start the cluster sequentially instead of concurrently. We received these errors when we started Roxie every time like that. Once we began running startup concurrently on every node we stopped getting these errors on startup. Since the deployment doesn’t finish at the same time on every node you can get these errors after almost every deployment.
Try stopping and restarting the cluster concurrently.
Bob
I think its related to some nodes having Roxie up and responding to requests while other nodes are not yet responding. When we first started using OSS some people were running the "for" loop to start the cluster sequentially instead of concurrently. We received these errors when we started Roxie every time like that. Once we began running startup concurrently on every node we stopped getting these errors on startup. Since the deployment doesn’t finish at the same time on every node you can get these errors after almost every deployment.
Try stopping and restarting the cluster concurrently.
Bob
- bforeman
- Community Advisory Board Member
- Posts: 1006
- Joined: Wed Jun 29, 2011 7:13 pm
Thanks bforeman , Your post addressed why so many error message raised, yesterday this slave node is down automatically, but master node is alive.
Could you please help find the reason why his slave node automatically shut down several times a day from attached log? Our roxie cluster has 1 master and only 1 slave, it's in production environment, so often shut down is a big risk for us.
Could you please help find the reason why his slave node automatically shut down several times a day from attached log? Our roxie cluster has 1 master and only 1 slave, it's in production environment, so often shut down is a big risk for us.
- kevinLv
- Posts: 11
- Joined: Thu Aug 15, 2013 3:20 am
3 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest