Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Partial siddhi apps are not get undeployed when receiver node fails for some cases. #783

Open
Ketharan opened this issue Sep 4, 2018 · 0 comments

Comments

@Ketharan
Copy link
Contributor

Ketharan commented Sep 4, 2018

Description:
Partial siddhi apps are not get undeployed when the worker node (with receiver configuration) fails for particular order of server initialization.

Suggested Labels:

Suggested Assignees:

@pcnfernando

Affected Product Version:
wso2sp-4.2.0

OS, DB, other environment details and versions:
Ubuntu 16.04 , Distributed deployment pattern wso2sp-4.2.0
Steps to reproduce:
Start the distributed distribution of wso2sp-4.2.0 in the following order. First the worker node then manager node and finally receiver node. Deploy a siddhi App and after the deployment finished quit the receiver node.

worker logs
manager logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants