lifeguard - Project Hosting on Google Code

Last 30 days Dec 22, 2009 r110 (calculates cost of running EC2 instances based on log file i...) committed by dkavanagh - calculates cost of running EC2 instances based on log file info about when instances started/stopped calculates cost of running EC2 instances based on log file info about when instances started/stopped Earlier this year Oct 07, 2009 r109 (supports parallel result file upload to S3, thanks Shlomo. i...) committed by dkavanagh - supports parallel result file upload to S3, thanks Shlomo. improved busy/idle tracking for better instance load value supports parallel result file upload to S3, thanks Shlomo. improved busy/idle tracking for better instance load value Oct 06, 2009 ScalingResults Wiki page edited by dkavanagh - Revision r107 Edited wiki page through web user interface. Revision r107 Edited wiki page through web user interface. Oct 05, 2009 r105 (pool manager now handles termination better. It tracks how m...) committed by dkavanagh - pool manager now handles termination better. It tracks how many instances are desired to kill, then when their time during the current billable hour elapses, they are terminated. This maximizes use of the instance billable hour and maintains termination desires of the pool. Also report now is the number of actual servers running, vs # servers started pool manager now handles termination better. It tracks how many instances are desired to kill, then when their time during the current billable hour elapses, they are terminated. This maximizes use of the instance billable hour and maintains termination desires of the pool. Also report now is the number of actual servers running, vs # servers started Oct 02, 2009 ScalingResults Wiki page edited by dkavanagh - Revision r104 Edited wiki page through web user interface. Revision r104 Edited wiki page through web user interface. Oct 02, 2009 ScalingResults Wiki page added by dkavanagh - Revision r103 Created wiki page through web user interface. Revision r103 Created wiki page through web user interface. Oct 02, 2009 r101 (fixed bug in terminate code that occurs when < all instances...) committed by dkavanagh - fixed bug in terminate code that occurs when < all instances are being terminated fixed bug in terminate code that occurs when < all instances are being terminated Sep 24, 2009 r100 (newer version of typica) committed by dkavanagh - newer version of typica newer version of typica Sep 24, 2009 r99 (break out reading of pool config into protected method. This...) committed by dkavanagh - break out reading of pool config into protected method. This allows overriding by child class and tweaking of pool config programatically. This is helpful for sending dynamic values in user data. break out reading of pool config into protected method. This allows overriding by child class and tweaking of pool config programatically. This is helpful for sending dynamic values in user data. Sep 24, 2009 r98 (changed instance list to Vector to avoid concurrent mod exce...) committed by dkavanagh - changed instance list to Vector to avoid concurrent mod exception. Now use greedy approach to reading status messages. 10 at a time isn't enough when there is a lot of status being reported. Can get behind an improperly assume instances are failing. improve proxxy handling changed instance list to Vector to avoid concurrent mod exception. Now use greedy approach to reading status messages. 10 at a time isn't enough when there is a lot of status being reported. Can get behind an improperly assume instances are failing. improve proxxy handling Sep 24, 2009 r97 (changed to "secret" for queue ) committed by dkavanagh - changed to "secret" for queue changed to "secret" for queue Aug 12, 2009 r96 (allow for ingestion based soley on properties (no files) ) committed by dkavanagh - allow for ingestion based soley on properties (no files) allow for ingestion based soley on properties (no files) Aug 12, 2009 r95 (allow input file to be null. Some requests just use properti...) committed by dkavanagh - allow input file to be null. Some requests just use properties allow input file to be null. Some requests just use properties Jul 16, 2009 r94 (support for eucalyptus.. testing pending.. support for doubl...) committed by dkavanagh - support for eucalyptus.. testing pending.. support for double/secret credentials. tested with old single credentials and still works. support for eucalyptus.. testing pending.. support for double/secret credentials. tested with old single credentials and still works. Jul 16, 2009 issue 7 (SQS2 Transition : invalid RECEIVE_COUNT) Status changed by dkavanagh - Thanks. I finally changed all of these values a few weeks ago. I've been able to use Lifeguard with the new queues, so I think this issue is all set. Status: Fixed Thanks. I finally changed all of these values a few weeks ago. I've been able to use Lifeguard with the new queues, so I think this issue is all set. Status: Fixed Jul 16, 2009 issue 6 (load average computation) Status changed by dkavanagh - I know it's been a long time. Last summer, I did some changes that greatly improved the load estimation of the service instances. I discussed this in the forum. Status: Fixed I know it's been a long time. Last summer, I did some changes that greatly improved the load estimation of the service instances. I discussed this in the forum. Status: Fixed Jul 16, 2009 issue 5 (Urgent- PROBLEM WITH TEXT TO PDF) Status changed by dkavanagh - Status: WontFix Status: WontFix Jul 16, 2009 issue 4 (Need help with video transcoding.) Status changed by dkavanagh - Status: WontFix Status: WontFix Jun 17, 2009 r93 (set default receive count to 10. Also print actual error whe...) committed by dkavanagh - set default receive count to 10. Also print actual error when server can't be started set default receive count to 10. Also print actual error when server can't be started Jun 07, 2009 r92 (changed default receive message count to 10 (to match new ma...) committed by dkavanagh - changed default receive message count to 10 (to match new max for new SQS API) changed default receive message count to 10 (to match new max for new SQS API) May 25, 2009 issue 7 (SQS2 Transition : invalid RECEIVE_COUNT) commented on by gummay - In 'workaround' section I of course meant =10, not >10 :) In 'workaround' section I of course meant =10, not >10 :) May 25, 2009 issue 7 (SQS2 Transition : invalid RECEIVE_COUNT) reported by gummay - What steps will reproduce the problem? 1. Run PoolManager from r91 of lifeguard (SQS2 upgrade), with RECEIVE_COUNT > 10 in StatusLogger.java or receiveCount >10 in PoolManager.java or receiveCount in conf/beans.xml What is the expected output? What do you see instead? Expect standard queue processing, instead get: SEVERE: Error reading message, Retrying. com.xerox.amazonws.sqs2.SQSException: Client error : (InvalidParameterValue) Value 20 for parameter MaxNumberOfMessages is invalid. Reason: Must be between 1 and 10, if provided. at com.xerox.amazonws.sqs2.MessageQueue.makeRequestInt(MessageQueue.java:483) at com.xerox.amazonws.sqs2.MessageQueue.receiveMessages(MessageQueue.java:245) at com.xerox.amazonws.sqs2.MessageQueue.receiveMessages(MessageQueue.java:182) at com.directthought.lifeguard.StatusLogger.run(StatusLogger.java:80) at java.lang.Thread.run(Thread.java:595) -or- com.xerox.amazonws.sqs2.SQSException: Client error : (InvalidParameterValue) Value 20 for parameter MaxNumberOfMessages is invalid. Reason: Must be between 1 and 10, if provided. at com.xerox.amazonws.sqs2.MessageQueue.makeRequestInt(MessageQueue.java:483) at com.xerox.amazonws.sqs2.MessageQueue.receiveMessages(MessageQueue.java:245) at com.xerox.amazonws.sqs2.MessageQueue.receiveMessages(MessageQueue.java:182) at com.directthought.lifeguard.PoolManager.run(PoolManager.java:212) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) What version of the product are you using? On what operating system? r91 from svn (with some local modifications) on Scientific Linux 4.7 Please provide any additional information below. Changing: RECEIVE_COUNT = 10 in StatusLogger.java receiveCount >10 in PoolManager.java receiveCount >10 in conf/beans.xml can be used as a work around. What steps will reproduce the problem? 1. Run PoolManager from r91 of lifeguard (SQS2 upgrade), with RECEIVE_COUNT > 10 in StatusLogger.java or receiveCount >10 in PoolManager.java or receiveCount in conf/beans.xml What is the expected output? What do you see instead? Expect standard queue processing, instead get: SEVERE: Error reading message, Retrying. com.xerox.amazonws.sqs2.SQSException: Client error : (InvalidParameterValue) Value 20 for parameter MaxNumberOfMessages is invalid. Reason: Must be between 1 and 10, if provided. at com.xerox.amazonws.sqs2.MessageQueue.makeRequestInt(MessageQueue.java:483) at com.xerox.amazonws.sqs2.MessageQueue.receiveMessages(MessageQueue.java:245) at com.xerox.amazonws.sqs2.MessageQueue.receiveMessages(MessageQueue.java:182) at com.directthought.lifeguard.StatusLogger.run(StatusLogger.java:80) at java.lang.Thread.run(Thread.java:595) -or- com.xerox.amazonws.sqs2.SQSException: Client error : (InvalidParameterValue) Value 20 for parameter MaxNumberOfMessages is invalid. Reason: Must be between 1 and 10, if provided. at com.xerox.amazonws.sqs2.MessageQueue.makeRequestInt(MessageQueue.java:483) at com.xerox.amazonws.sqs2.MessageQueue.receiveMessages(MessageQueue.java:245) at com.xerox.amazonws.sqs2.MessageQueue.receiveMessages(MessageQueue.java:182) at com.directthought.lifeguard.PoolManager.run(PoolManager.java:212) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) What version of the product are you using? On what operating system? r91 from svn (with some local modifications) on Scientific Linux 4.7 Please provide any additional information below. Changing: RECEIVE_COUNT = 10 in StatusLogger.java receiveCount >10 in PoolManager.java receiveCount >10 in conf/beans.xml can be used as a work around. May 07, 2009 r91 (patch submitted by shlomo to launch replacement server befor...) committed by dkavanagh - patch submitted by shlomo to launch replacement server before trying to terminate faulty one patch submitted by shlomo to launch replacement server before trying to terminate faulty one May 07, 2009 r90 (changes to upgrade to new SQS api. Lower costs, same great s...) committed by dkavanagh - changes to upgrade to new SQS api. Lower costs, same great service changes to upgrade to new SQS api. Lower costs, same great service May 04, 2009 issue 5 (Urgent- PROBLEM WITH TEXT TO PDF) commented on by baldr...@free.fr - Change the semi-colons (;) to colons (:) in the -classpath part of ingest.sh. Change the semi-colons (;) to colons (:) in the -classpath part of ingest.sh. Older Sep 11, 2008 r89 (completed movement of lifeguard gui into lifeguard dir. adde...) committed by dkavanagh - completed movement of lifeguard gui into lifeguard dir. added ability to specify additional params in user data to service instances completed movement of lifeguard gui into lifeguard dir. added ability to specify additional params in user data to service instances Sep 11, 2008 r88 ( moving lifeguard GUI items out of root, to ease integration...) committed by dkavanagh - moving lifeguard GUI items out of root, to ease integration with other apps moving lifeguard GUI items out of root, to ease integration with other apps Sep 10, 2008 HelpfulTips Wiki page edited by dkavanagh Sep 09, 2008 r86 (allow base service class to bump out busy/idle times since i...) committed by dkavanagh - allow base service class to bump out busy/idle times since it really has current info about that state. allow base service class to bump out busy/idle times since it really has current info about that state. Sep 09, 2008 r85 (updated PoolMonitor interface and related code. Added Pool L...) committed by dkavanagh - updated PoolMonitor interface and related code. Added Pool Load to Flex UI updated PoolMonitor interface and related code. Added Pool Load to Flex UI Sep 05, 2008 r84 (code to properly handle propery based ingestion (no input fi...) committed by dkavanagh - code to properly handle propery based ingestion (no input file). code to properly handle propery based ingestion (no input file). Aug 28, 2008 r83 (Lots of stuff. Better instance status (they always send stat...) committed by dkavanagh - Lots of stuff. Better instance status (they always send status.. and it is used as a heart beat) Instance monitor will terminate and replace failed instances (whose heartbeat has not been heard in long enough time) Can now override output keys either in the service or in the work request can override instance id in service config file (so it will not try to pull instance metadata till it times out) new ingestor base class methods to import data several ways, files, objs already in S3 or just empty input and properties. decent proxy handling, so this can run behind a proxy. Lots of stuff. Better instance status (they always send status.. and it is used as a heart beat) Instance monitor will terminate and replace failed instances (whose heartbeat has not been heard in long enough time) Can now override output keys either in the service or in the work request can override instance id in service config file (so it will not try to pull instance metadata till it times out) new ingestor base class methods to import data several ways, files, objs already in S3 or just empty input and properties. decent proxy handling, so this can run behind a proxy. Aug 08, 2008 HelpfulTips Wiki page edited by dkavanagh Aug 07, 2008 HelpfulTips Wiki page added by dkavanagh Aug 04, 2008 r80 (patch from Chris to properly set all status message fields ) committed by dkavanagh - patch from Chris to properly set all status message fields patch from Chris to properly set all status message fields Aug 04, 2008 r79 (patch from Andrey to properly set mime type on files stored ...) committed by dkavanagh - patch from Andrey to properly set mime type on files stored in S3 patch from Andrey to properly set mime type on files stored in S3 Aug 04, 2008 r78 (patch from Chris to only sleep when no messages were process...) committed by dkavanagh - patch from Chris to only sleep when no messages were processed (speeds up status message processing) patch from Chris to only sleep when no messages were processed (speeds up status message processing) Aug 04, 2008 r77 (removed my proxy setting ) committed by dkavanagh - removed my proxy setting removed my proxy setting

issue 7 (SQS2 Transition : invalid RECEIVE_COUNT) reported by gummay - What steps will reproduce the problem? 1. Run PoolManager from r91 of lifeguard (SQS2 upgrade), with RECEIVE_COUNT > 10 in StatusLogger.java or receiveCount >10 in PoolManager.java or receiveCount in conf/beans.xml What is the expected output? What do you see instead? Expect standard queue processing, instead get: SEVERE: Error reading message, Retrying. com.xerox.amazonws.sqs2.SQSException: Client error : (InvalidParameterValue) Value 20 for parameter MaxNumberOfMessages is invalid. Reason: Must be between 1 and 10, if provided. at com.xerox.amazonws.sqs2.MessageQueue.makeRequestInt(MessageQueue.java:483) at com.xerox.amazonws.sqs2.MessageQueue.receiveMessages(MessageQueue.java:245) at com.xerox.amazonws.sqs2.MessageQueue.receiveMessages(MessageQueue.java:182) at com.directthought.lifeguard.StatusLogger.run(StatusLogger.java:80) at java.lang.Thread.run(Thread.java:595) -or- com.xerox.amazonws.sqs2.SQSException: Client error : (InvalidParameterValue) Value 20 for parameter MaxNumberOfMessages is invalid. Reason: Must be between 1 and 10, if provided. at com.xerox.amazonws.sqs2.MessageQueue.makeRequestInt(MessageQueue.java:483) at com.xerox.amazonws.sqs2.MessageQueue.receiveMessages(MessageQueue.java:245) at com.xerox.amazonws.sqs2.MessageQueue.receiveMessages(MessageQueue.java:182) at com.directthought.lifeguard.PoolManager.run(PoolManager.java:212) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) What version of the product are you using? On what operating system? r91 from svn (with some local modifications) on Scientific Linux 4.7 Please provide any additional information below. Changing: RECEIVE_COUNT = 10 in StatusLogger.java receiveCount >10 in PoolManager.java receiveCount >10 in conf/beans.xml can be used as a work around.

What steps will reproduce the problem? 1. Run PoolManager from r91 of lifeguard (SQS2 upgrade), with RECEIVE_COUNT > 10 in StatusLogger.java or receiveCount >10 in PoolManager.java or receiveCount in conf/beans.xml What is the expected output? What do you see instead? Expect standard queue processing, instead get: SEVERE: Error reading message, Retrying. com.xerox.amazonws.sqs2.SQSException: Client error : (InvalidParameterValue) Value 20 for parameter MaxNumberOfMessages is invalid. Reason: Must be between 1 and 10, if provided. at com.xerox.amazonws.sqs2.MessageQueue.makeRequestInt(MessageQueue.java:483) at com.xerox.amazonws.sqs2.MessageQueue.receiveMessages(MessageQueue.java:245) at com.xerox.amazonws.sqs2.MessageQueue.receiveMessages(MessageQueue.java:182) at com.directthought.lifeguard.StatusLogger.run(StatusLogger.java:80) at java.lang.Thread.run(Thread.java:595) -or- com.xerox.amazonws.sqs2.SQSException: Client error : (InvalidParameterValue) Value 20 for parameter MaxNumberOfMessages is invalid. Reason: Must be between 1 and 10, if provided. at com.xerox.amazonws.sqs2.MessageQueue.makeRequestInt(MessageQueue.java:483) at com.xerox.amazonws.sqs2.MessageQueue.receiveMessages(MessageQueue.java:245) at com.xerox.amazonws.sqs2.MessageQueue.receiveMessages(MessageQueue.java:182) at com.directthought.lifeguard.PoolManager.run(PoolManager.java:212) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) What version of the product are you using? On what operating system? r91 from svn (with some local modifications) on Scientific Linux 4.7 Please provide any additional information below. Changing: RECEIVE_COUNT = 10 in StatusLogger.java receiveCount >10 in PoolManager.java receiveCount >10 in conf/beans.xml can be used as a work around.

Last 30 days

Earlier this year

Older