Hi Glenn,

ok, thanks for the information.
So this means we are talking about network sessions, good to know.

Tanks for your help.

Kind regards
Christian

> On 04 Apr 2016, at 09:25, Glenn Wagner <[email protected]> wrote:
> 
> Hi,
> 
> To find out how many sessions are connected to the SSVM you can run 
> 
> netstat -anp | grep ESTABLISHED
> 
> Thanks
> Glenn
> 
> 
> Regards,
> 
> Glenn Wagner
> 
> [email protected] 
> www.shapeblue.com
> 2nd Floor, Oudehuis Centre, 122 Main Rd, Somerset West, Cape Town  7130South 
> Africa
> @shapeblue
> 
> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] 
> Sent: Monday, 04 April 2016 9:21 AM
> To: [email protected]
> Subject: Re: Secondary Storage VM overloaded
> 
> Hi Dag,
> 
> thanks for your reply.
> 
> Unfortunately we actually don’t have a clue what kind of sessions are meant.
> Do we need to monitor ssh sessions, linux processes or some kind of java 
> sessions?
> 
> Do you have any idea where we can start?
> 
> Kind Regards
> Christian
> 
>> On 01 Apr 2016, at 12:19, Dag Sonstebo <[email protected]> wrote:
>> 
>> Hi Christian,
>> 
>> I think to find the actual usage figures over time you would have to monitor 
>> the sessions locally on the SSVM, I can't see anything in the API to query 
>> this.
>> 
>> One way to determine this is to lower the secstorage.sessions.max figure and 
>> monitor how often a second SSVM is spawned. Also keep in mind you could 
>> increase the service offering for system VMs to increase the capacity the 
>> SSVM can handle, this could negate the requirement for multiple SSVM 
>> instances.
>> 
>> Dag Sonstebo
>> Cloud Architect
>> ShapeBlue
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> On 01/04/2016, 10:10, "[email protected]" 
>> <[email protected]> wrote:
>> 
>>> Hi all,
>>> 
>>> I have a question regarding the scalability of the ssvm.
>>> As I understood cloudstack is able to scale out the ssvm, so that a new one 
>>> is created when the load is to high.
>>> To achieve this we have to edit the two global settings 
>>> secstorage.capacity.standby and secstorage.session.max, but we have no idea 
>>> what values are rational.
>>> 
>>> Is there a way to see the current values, so that we can derive the new 
>>> value which we want to use?
>>> I mean if the current ssvm needs just 10 sessions to be overloaded and we 
>>> set the secstorage.session.max to 20, cloudstack will never spawn a new 
>>> ssvm.
>>> 
>>> Kind Regards
>>> Christian
>> 
>> Regards,
>> 
>> Dag Sonstebo
>> 
>> [email protected]
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
> 

Reply via email to