You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by ch...@zv.fraunhofer.de on 2016/04/01 11:10:41 UTC
Secondary Storage VM overloaded
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
Re: Secondary Storage VM overloaded
Posted by ch...@zv.fraunhofer.de.
Hi,
a few minutes ago I discovered that there is a “Active Sessions” field in the details pane of the SSVMs, but the value is blank.
Do I need to configure something else so that cloudstack is aware of the sessions of the SSVM?
Kind Regards
Christian
> On 04 Apr 2016, at 09:33, Kirmse, Christian <ch...@zv.fraunhofer.de> wrote:
>
> 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 <gl...@shapeblue.com> 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
>>
>> glenn.wagner@shapeblue.com
>> www.shapeblue.com
>> 2nd Floor, Oudehuis Centre, 122 Main Rd, Somerset West, Cape Town 7130South Africa
>> @shapeblue
>>
>> -----Original Message-----
>> From: christian.kirmse@zv.fraunhofer.de [mailto:christian.kirmse@zv.fraunhofer.de]
>> Sent: Monday, 04 April 2016 9:21 AM
>> To: users@cloudstack.apache.org
>> 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 <Da...@shapeblue.com> 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, "christian.kirmse@zv.fraunhofer.de" <ch...@zv.fraunhofer.de> 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
>>>
>>> Dag.Sonstebo@shapeblue.com
>>> www.shapeblue.com
>>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue
>>
>
Re: Secondary Storage VM overloaded
Posted by ch...@zv.fraunhofer.de.
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 <gl...@shapeblue.com> 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
>
> glenn.wagner@shapeblue.com
> www.shapeblue.com
> 2nd Floor, Oudehuis Centre, 122 Main Rd, Somerset West, Cape Town 7130South Africa
> @shapeblue
>
> -----Original Message-----
> From: christian.kirmse@zv.fraunhofer.de [mailto:christian.kirmse@zv.fraunhofer.de]
> Sent: Monday, 04 April 2016 9:21 AM
> To: users@cloudstack.apache.org
> 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 <Da...@shapeblue.com> 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, "christian.kirmse@zv.fraunhofer.de" <ch...@zv.fraunhofer.de> 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
>>
>> Dag.Sonstebo@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue
>
RE: Secondary Storage VM overloaded
Posted by Glenn Wagner <gl...@shapeblue.com>.
Hi,
To find out how many sessions are connected to the SSVM you can run
netstat -anp | grep ESTABLISHED
Thanks
Glenn
Regards,
Glenn Wagner
glenn.wagner@shapeblue.com
www.shapeblue.com
2nd Floor, Oudehuis Centre, 122 Main Rd, Somerset West, Cape Town 7130South Africa
@shapeblue
-----Original Message-----
From: christian.kirmse@zv.fraunhofer.de [mailto:christian.kirmse@zv.fraunhofer.de]
Sent: Monday, 04 April 2016 9:21 AM
To: users@cloudstack.apache.org
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 <Da...@shapeblue.com> 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, "christian.kirmse@zv.fraunhofer.de" <ch...@zv.fraunhofer.de> 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
>
> Dag.Sonstebo@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue
Re: Secondary Storage VM overloaded
Posted by ch...@zv.fraunhofer.de.
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 <Da...@shapeblue.com> 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, "christian.kirmse@zv.fraunhofer.de" <ch...@zv.fraunhofer.de> 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
>
> Dag.Sonstebo@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
Re: Secondary Storage VM overloaded
Posted by Dag Sonstebo <Da...@shapeblue.com>.
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, "christian.kirmse@zv.fraunhofer.de" <ch...@zv.fraunhofer.de> 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
Dag.Sonstebo@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue