[Dev] How can we reduce the frequency of the error No application members available being printed at ELB side, when all members of a cluster are down?

2014-09-01 Thread Evanthika Amarasiri 
Hi,

Recently, when testing API-M, DSS with ELB 2.1.1, we noticed the log files
of ELB growing up to hundreds of GBs. See [1]. The reason was that due to a
network failure or some other reason, all the nodes of the cluster were
removed from the cluster and the below error was printing continuously
creating log files of about 100GB.

*TID: [0] [ELB] [2014-08-26 05:19:52,131] ERROR
{org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint} -  No
application members available
{org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint}*

*TID: [0] [ELB] [2014-08-26 05:19:52,131] ERROR
{org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint} -  No
application members available
{org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint}*

So is there a way we can reduce the frequency of this error being printed?
Right now, I suppose it's being printed every millisecond/second. Is there
any way that we can print this maybe every 10-15 minutes or make it
configurable?

[1] - https://wso2.org/jira/browse/LB-164

Regards,

Evanthika
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How can we reduce the frequency of the error No application members available being printed at ELB side, when all members of a cluster are down?

2014-09-01 Thread Kasun Gajasinghe 
Hi,

AFAIK, this log is printed for each request if there are no nodes in the
cluster to serve those requests. If there request is for a worker, then
there should at least be one worker node in the cluster.

I guess we can make this a DEBUG log since the http response also contain
this error?

Regards,
KasunG


On Mon, Sep 1, 2014 at 1:56 PM, Evanthika Amarasiri evanth...@wso2.com
wrote:

 Hi,

 Recently, when testing API-M, DSS with ELB 2.1.1, we noticed the log files
 of ELB growing up to hundreds of GBs. See [1]. The reason was that due to a
 network failure or some other reason, all the nodes of the cluster were
 removed from the cluster and the below error was printing continuously
 creating log files of about 100GB.

 *TID: [0] [ELB] [2014-08-26 05:19:52,131] ERROR
 {org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint} -  No
 application members available
 {org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint}*

 *TID: [0] [ELB] [2014-08-26 05:19:52,131] ERROR
 {org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint} -  No
 application members available
 {org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint}*

 So is there a way we can reduce the frequency of this error being printed?
 Right now, I suppose it's being printed every millisecond/second. Is there
 any way that we can print this maybe every 10-15 minutes or make it
 configurable?

 [1] - https://wso2.org/jira/browse/LB-164

 Regards,

 Evanthika

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How can we reduce the frequency of the error No application members available being printed at ELB side, when all members of a cluster are down?

2014-09-01 Thread Afkham Azeez 
The quickest would be to set the log level to FATAL for that logger, NOT
change the code  issue a PATCH to change the log level to debug!


On Mon, Sep 1, 2014 at 2:28 PM, Kasun Gajasinghe kas...@wso2.com wrote:

 Hi,

 AFAIK, this log is printed for each request if there are no nodes in the
 cluster to serve those requests. If there request is for a worker, then
 there should at least be one worker node in the cluster.

 I guess we can make this a DEBUG log since the http response also contain
 this error?

 Regards,
 KasunG


  On Mon, Sep 1, 2014 at 1:56 PM, Evanthika Amarasiri evanth...@wso2.com
 wrote:

  Hi,

 Recently, when testing API-M, DSS with ELB 2.1.1, we noticed the log
 files of ELB growing up to hundreds of GBs. See [1]. The reason was that
 due to a network failure or some other reason, all the nodes of the cluster
 were removed from the cluster and the below error was printing continuously
 creating log files of about 100GB.

 *TID: [0] [ELB] [2014-08-26 05:19:52,131] ERROR
 {org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint} -  No
 application members available
 {org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint}*

 *TID: [0] [ELB] [2014-08-26 05:19:52,131] ERROR
 {org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint} -  No
 application members available
 {org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint}*

 So is there a way we can reduce the frequency of this error being
 printed? Right now, I suppose it's being printed every millisecond/second.
 Is there any way that we can print this maybe every 10-15 minutes or make
 it configurable?

 [1] - https://wso2.org/jira/browse/LB-164

 Regards,

 Evanthika

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --

 *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
 email: kasung AT spamfree wso2.com
 linked-in: http://lk.linkedin.com/in/gajasinghe
 blog: http://kasunbg.org






-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/*
*email: **az...@wso2.com* az...@wso2.com
* cell: +94 77 3320919 blog: **http://blog.afkham.org*
http://blog.afkham.org
*twitter: **http://twitter.com/afkham_azeez*
http://twitter.com/afkham_azeez
* linked-in: **http://lk.linkedin.com/in/afkhamazeez
http://lk.linkedin.com/in/afkhamazeez*

*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev