Great. So we can use same AS API for VM cluster monitor updating.. right?
On Mon, Oct 13, 2014 at 11:58 AM, Reka Thirunavukkarasu
wrote:
> +1. This will be nice to have. So, with this feature we can dynamically
> update the cluster monitor.
>
> Thanks,
> Reka
>
> On Mon, Oct 13, 2014 at 8:43 AM,
+1. This will be nice to have. So, with this feature we can dynamically
update the cluster monitor.
Thanks,
Reka
On Mon, Oct 13, 2014 at 8:43 AM, Nirmal Fernando
wrote:
> Hi All,
>
> I've implemented $subject for Kubernetes - Docker scenario.
>
> *Implementation Details:*
>
> Autoscaler provide
Hi
I have fixed them and committed it. Now that hierarchical monitors with the
given definition is working fine..
Thanks,
Reka
On Mon, Oct 13, 2014 at 12:19 AM, Isuru Haththotuwa
wrote:
>
>
> On Mon, Oct 13, 2014 at 12:03 AM, Reka Thirunavukkarasu
> wrote:
>
>> Thanks Isuru for pointing out..
On Mon, Oct 13, 2014 at 11:13 AM, Isuru Perera wrote:
> We should remove the duplicate class name from logs
>
+1
>
> On Mon, Oct 13, 2014 at 9:15 AM, Imesh Gunaratne wrote:
>
>>
>>> in og4j.appender.CARBON_LOGFILE.layout.ConversionPattern=TID: [%T] [%S]
>>> [%d] %P%5p *{%c}* - %x %m* {%c}*%n
>>
Hi,
CEP extension FaultHandlingWindowProcessor removing a terminated member
from the map. But after a while, it is complaining it as a faulty member.
Here is the log. MemberId highlighted.
TID: [0] [STRATOS] [2014-10-13 11:15:22,409] DEBUG
{org.apache.stratos.autoscaler.rule.RuleTasksDelegator} -
We should remove the duplicate class name from logs
On Mon, Oct 13, 2014 at 9:15 AM, Imesh Gunaratne wrote:
>
>> in og4j.appender.CARBON_LOGFILE.layout.ConversionPattern=TID: [%T] [%S]
>> [%d] %P%5p *{%c}* - %x %m* {%c}*%n
>> %c appears twice, which lets the class name to logged twice
>>
>> This
[
https://issues.apache.org/jira/browse/STRATOS-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168969#comment-14168969
]
ASF GitHub Bot commented on STRATOS-791:
Github user swgkg commented on the pull
[
https://issues.apache.org/jira/browse/STRATOS-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168967#comment-14168967
]
ASF GitHub Bot commented on STRATOS-791:
GitHub user swgkg opened a pull request:
Github user swgkg commented on the pull request:
https://github.com/apache/stratos/pull/87#issuecomment-58847370
New pull request -
https://github.com/apache/stratos/pull/91
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
[
https://issues.apache.org/jira/browse/STRATOS-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168965#comment-14168965
]
ASF GitHub Bot commented on STRATOS-791:
Github user swgkg closed the pull reques
GitHub user swgkg opened a pull request:
https://github.com/apache/stratos/pull/91
Fixes for error in publishing artifact updated event - STRATOS-791
This pull image contains the fixes for :
Error in publishing artifact updated event - STRATOS-858
Re factoring the code - STRA
[
https://issues.apache.org/jira/browse/STRATOS-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168964#comment-14168964
]
ASF GitHub Bot commented on STRATOS-791:
Github user swgkg commented on the pull
Github user swgkg closed the pull request at:
https://github.com/apache/stratos/pull/87
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
Github user swgkg commented on the pull request:
https://github.com/apache/stratos/pull/87#issuecomment-58847215
Will add a new pull request
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have th
>
>
> in og4j.appender.CARBON_LOGFILE.layout.ConversionPattern=TID: [%T] [%S]
> [%d] %P%5p *{%c}* - %x %m* {%c}*%n
> %c appears twice, which lets the class name to logged twice
>
> This is the convention used in carbon server logs.
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member,
Hi All,
I've implemented $subject for Kubernetes - Docker scenario.
*Implementation Details:*
Autoscaler provides an API to update a cluster monitor created for a
particular cluster, by accepting set of properties. Autoscaler API
implementation delegates such a request to relevant cluster monito
On Mon, Oct 13, 2014 at 12:03 AM, Reka Thirunavukkarasu
wrote:
> Thanks Isuru for pointing out..
>
> Since i got to restarted while i was testing, i didn't face this issue.
> When i tried with the fresh setup, i faced the same issue..I did a fix for
> this. Will test it and update on it..
>
Great
Thanks Isuru for pointing out..
Since i got to restarted while i was testing, i didn't face this issue.
When i tried with the fresh setup, i faced the same issue..I did a fix for
this. Will test it and update on it..
Thanks,
Reka
On Sun, Oct 12, 2014 at 11:55 PM, Isuru Haththotuwa
wrote:
> My
My Application is something similar to below:
[image: Inline image 1]
Both the cluster php1, php2 are notifying the parent as they are Activated.
Also the group1 is also notifying the parent as its Activated. However,
seems the group2 is not notifying the parent of its activation. Looking in
[
https://issues.apache.org/jira/browse/STRATOS-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nirmal Fernando reassigned STRATOS-716:
---
Assignee: Nirmal Fernando
> Support for manual scaling
> --
Yes Manula. Now it is solved. Thanks.
On Sun, Oct 12, 2014 at 5:33 PM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:
> Hi Raj,
>
> This issue is fixed now. I have perform a build and it builds successfully.
>
> Thanks !
>
> On Sat, Oct 11, 2014 at 7:41 PM, Rajkumar Rajaratnam
> wrote
Hi Reka,
Great news!!
I tried with a similar Application, however there were no instance spawned
for the top level Cartridge. But, both the Groups were successfully
activated. Might be an issue with the definitions I used, have attached
there here. Will check on this more.
On Sun, Oct 12, 2014
Hi Chamila,
There is no particular reason for that. At the time we have develop this
functionality we have test it without having this property in config.
Thanks for figure it out. +1 for the new change.
Thanks !
On Sat, Oct 11, 2014 at 9:25 PM, Nirmal Fernando
wrote:
> +1, please send a PR :)
Hi Raj,
This issue is fixed now. I have perform a build and it builds successfully.
Thanks !
On Sat, Oct 11, 2014 at 7:41 PM, Rajkumar Rajaratnam
wrote:
> Hi,
>
> Master branch build is failing. Here is the trace.
>
> [INFO]
> ---
Hi Martin,
Sorry for the late response.
On Sun, Oct 12, 2014 at 11:25 AM, Reka Thirunavukkarasu
wrote:
> Hi Martin,
>
> On Fri, Oct 10, 2014 at 5:40 AM, Martin Eppel (meppel)
> wrote:
>
>> Hi Reka,
>>
>>
>>
>> I did some startup order / dependency testing and run into the issue that
>> when a
Hi Martin,
You can find more details about profile in [1].
[1]
https://cwiki.apache.org/confluence/display/STRATOS/4.0.0+Starting+Apache+Stratos
Thanks !
On Sat, Oct 11, 2014 at 9:54 PM, Nirmal Fernando
wrote:
> Hi Martin,
>
> When we normally start the server, it uses default profile. But if
Nirmal Fernando created STRATOS-889:
---
Summary: Move all drools files to a new folder under
repository/conf
Key: STRATOS-889
URL: https://issues.apache.org/jira/browse/STRATOS-889
Project: Stratos
Nirmal Fernando created STRATOS-888:
---
Summary: [MQTT] When debug logs enabled for Messaging component -
messaging model dead locks
Key: STRATOS-888
URL: https://issues.apache.org/jira/browse/STRATOS-888
Nirmal Fernando created STRATOS-887:
---
Summary: Intermittent failure on receiving ClusterRemovedEvent at
Autoscaler
Key: STRATOS-887
URL: https://issues.apache.org/jira/browse/STRATOS-887
Project: St
29 matches
Mail list logo
