Hi Sathwik,
I attached the patch to the JIRA ODE-563. All the changes are available in
the patch.
regards,
Sudharma
On 30 June 2015 at 18:43, Sathwik B P wrote:
> Hi Sudharma,
>
> Can you contribute your code as patch and attach it to the JIRA ODE-563.
>
> You could create the patch file in th
Hi Sudharma,
Can you contribute your code as patch and attach it to the JIRA ODE-563.
You could create the patch file in this way.
git diff master ODECluster > cluster_patch1.patch
Make sure all your changes are available in the patch.
regards,
sathwik
On Wed, Jun 17, 2015 at 12:51 PM, sudharm
Hi Sathwik,
I modified the code as you explained. You can go through the code by
following link.
https://github.com/Subasinghe/ode/tree/ODECluster
It would be helpful if you can provide a feedback on this.
Thank you.
On 10 June 2015 at 12:39, sudharma subasinghe wrote:
> Hi Sathwik,
>
> I tri
Hi Sathwik,
I tried to implement your logic also. Following is the link for committed
code upto now.
https://github.com/Subasinghe/ode/tree/ODECluster
I used info msgs to debugging as it can be observed easily in console. When
releasing the lock acquired by poller or web service the state is set
Hi Sathwik,
I will concern your approach. Thank you for your effort.
On 6 June 2015 at 18:43, Sathwik B P wrote:
> I have attached to the JIRA https://issues.apache.org/jira/browse/ODE-563
>
> On Sat, Jun 6, 2015 at 5:55 PM, sudharma subasinghe >
> wrote:
>
> > Hi Sathwik,
> >
> > I can't find
I have attached to the JIRA https://issues.apache.org/jira/browse/ODE-563
On Sat, Jun 6, 2015 at 5:55 PM, sudharma subasinghe
wrote:
> Hi Sathwik,
>
> I can't find the attached document. Please kind be enough to resend it.
>
> On 6 June 2015 at 15:42, Sathwik B P wrote:
>
> > Refer this one as
Hi Sathwik,
I can't find the attached document. Please kind be enough to resend it.
On 6 June 2015 at 15:42, Sathwik B P wrote:
> Refer this one as I have corrected the numbering of steps.
>
> On Sat, Jun 6, 2015 at 3:33 PM, Sathwik B P wrote:
>
>> Hi Sudharma/Tammo,
>>
>> Kindly review attach
Refer this one as I have corrected the numbering of steps.
On Sat, Jun 6, 2015 at 3:33 PM, Sathwik B P wrote:
> Hi Sudharma/Tammo,
>
> Kindly review attached document on my proposed approach. Let me know if
> you have any concerns or doubts on it.
>
> regards,
> sathwik
>
> On Fri, Jun 5, 2015 a
Hi Sudharma/Tammo,
Kindly review attached document on my proposed approach. Let me know if you
have any concerns or doubts on it.
regards,
sathwik
On Fri, Jun 5, 2015 at 6:56 PM, Sathwik B P wrote:
> find response inline
>
> On Wed, Jun 3, 2015 at 10:22 PM, sudharma subasinghe <
> suba...@cse.
find response inline
On Wed, Jun 3, 2015 at 10:22 PM, sudharma subasinghe
wrote:
> Hi,
>
> Sorry for the late reply. I was trying to achieve a proper solution.
> Following is my approach.
>
> 1) I elected master node for deploying purpose. So when a master node goes
> down hazelcast will elect t
Hi,
Sorry for the late reply. I was trying to achieve a proper solution.
Following is my approach.
1) I elected master node for deploying purpose. So when a master node goes
down hazelcast will elect the next oldest node for master.
2) ODEServer can identify whether clustering is enabled or not
Sudharma,
Any updates?
regards,
sathwik
On Fri, May 29, 2015 at 5:26 PM, Sathwik B P wrote:
> Sudharma,
>
> Can you elaborate on your option 1).
>
> Response to your option 2).
>
> Process Store is the component that handles process metadata,
> compilation and deployment in ODE. Integratio
Sudharma,
Can you elaborate on your option 1).
Response to your option 2).
Process Store is the component that handles process metadata,
compilation and deployment in ODE. Integration layers in ODE (Axis2, JBI)
use the process store.
Future implementations of IL for ODE will also use the
Hi,
I understood the problem within dynamic master/slave configuration. In my
approach, when a deployment request is routed to a slave node there will
not be a deployment. I suggest two options to avoid it.
1) Have static master/slave configuration only for deploy process
2) Modify the deployment
Sudharma,
We definitely need a master/slave in the hazelcast cluster. This is
probably needed for the job migration in the Scheduler to migrate the jobs
associated with a down node. Let hold on this topic for future discussion.
Going by the explanation where the master/slave nodes have certain
pr
Hi,
I will explain my approach as much as possible. The oldest node in the
hazelcast cluster is elected as the master node. In the failure of the
master node, next oldest node will be elected as the master node. This
master-slave configuration is just for deployment. When the hazelcast
cluster ele
Nandika,
I very well understand what you have put across, but it's secondary to me
now.
Sudharma,
My primary concern is to understand at a high level the deployment
architecture and how would master-slave configuration fit in. Are there any
restrictions imposed by the in-progress design?
Firstly
Hi Sathwik,
According to my understanding, in the clustering scenario, the master node
should perform all the deployment actions and the slave nodes also need to
perform some deployment actions. For example, the slave nodes also should
handle the process ACTIVATED event so that the process configu
Sudharma,
Where are you going to configure the master-slaves, is it in the web
application level or at the load balancer?
regards,
sathwik
On Tue, May 26, 2015 at 7:42 PM, sudharma subasinghe
wrote:
> Hi Tammo,
>
> Can you suggest the best method from these to implement? As first I
> suggested
Hi Tammo,
Can you suggest the best method from these to implement? As first I
suggested the master-slaves scenario I think it is easy to implement than
distributed lock scenario. However if you can suggest one from these two,
then I can think about it.
Thank you
On 21 May 2015 at 12:40, Sathwik
With respect to the hotdeployment,
We can drop the deployment archive onto the deployment folder. Since the
DeploymentPoller are acquiring the distributed lock for the DeploymentUnit,
only one of the nodes will get the lock and initiate the deployment.
DeploymentPollers on other nodes will fail in
Hi Tammo,
The distributed lock acquisition on the DeploymentUnit should be added to
both DeploymentWebService and DeploymentPoller.
When a deployment operation is initiated through the DeploymentWebService,
The load balancer routes it to any of the available nodes.
On the routed node, the Deploy
Hi Sudharma,
what do you expect from the "other nodes deployment"? Compilation is not
needed since the CBP file is written to the (shared) FS. Registration is
also not needed, since it is done via the shared database. So the only
thing that might be needed is to tell the engine that there is a new
Hi Tammo,
The master node writes meta data. But runtime information must be available
in all nodes.Since the folder is shared, all nodes will see the
availability of a new process. My idea is for master node to write the meta
data and other nodes to just read the meta data and load process.So we n
Hi Sathwik,
On Wed, May 20, 2015 at 6:40 AM, Sathwik B P wrote:
> Sudharma/Tammo,
>
> 1) How do we plan to decide which is the master node in the cluster?
>
I think the easiest approach is to always elect the oldest node in the
cluster to be the master. AFAIK Hazelcast can easily asked for this
Sudharma/Tammo,
1) How do we plan to decide which is the master node in the cluster?
2) Don't we need to stall the Deployment Pollers in the slave nodes?
Suggestion:
I am not sure whether do we need Master-SLaves. Why not give every node in
the cluster the same status (Active-Active).
When a n
Hi Sudharma,
Electing one master that is able to deploy is the right approach. Since the
metadata of a deployment is written to the database and the database is
shared among all nodes, sending notifications is not necessary. This is all
under the assumption that all nodes share the same deployment
Hi,
In the cluster, every node shares the database and deployment directory. To
avoid race condition I am going to introduce master and slave
configuration. Here master node will deploy the process and write the
version number to the database. Until master node finishes its process all
the salve n
28 matches
Mail list logo
