[jira] [Updated] (OAK-10455) Synchronous commit

2023-11-28 Thread Julian Reschke (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-10455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-10455:
-
Component/s: (was: commons)

> Synchronous commit
> --
>
> Key: OAK-10455
> URL: https://issues.apache.org/jira/browse/OAK-10455
> Project: Jackrabbit Oak
>  Issue Type: Bug
>Affects Versions: 1.48.0
>Reporter: Nitul
>Priority: Blocker
>
> We are using 1.48.0 version of oak-jcr. Out application stores the nodes and 
> retrive it.
> We are using multiple pods of this application. and consider below scenario 
> which is creating issue.
>  
> *Issue:*
> We have two request as below:
> Create some node and save it.- this is routed from pod1. (this will be saved 
> into mongo db after 1000ms with BackgroundUpdateOperation thread)
> Get created nodes - this is routed from pod2. (As this second request 
> immediately executed, for pod2 recently created data is not available. )
> How we can commit the changes in synchronised manner.
>  
> *Code:*
> {code:java}
>  LeaseCheckMode leaseCheckMode = Boolean.TRUE.equals(enableLeaseCheck) ? 
> LeaseCheckMode.STRICT
> : LeaseCheckMode.DISABLED;
> documentNodeStore = new MongoDocumentNodeStoreBuilder()
> .setMongoDB(getMongoURI(), mongoDbName, 16)
> .setLeaseCheckMode(leaseCheckMode)
> .build();
>Repository repository = new Jcr(new 
> Oak(documentNodeStore)).createRepository();
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (OAK-10455) synchronous commit

2023-09-25 Thread Nitul (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-10455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitul updated OAK-10455:

Summary: synchronous commit  (was: Data synchronisation between two pods)

> synchronous commit
> --
>
> Key: OAK-10455
> URL: https://issues.apache.org/jira/browse/OAK-10455
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: commons
>Affects Versions: 1.48.0
>Reporter: Nitul
>Priority: Blocker
>
> We are using 1.48.0 version of oak-jcr. Out application stores the nodes and 
> retrive it.
> We are using multiple pods of this application. and consider below scenario 
> which is creating issue.
>  
> *Issue:*
> We have two request as below:
> Create some node and save it.- this is routed from pod1. (this will be saved 
> into mongo db after 1000ms with BackgroundUpdateOperation thread)
> Get created nodes - this is routed from pod2. (As this second request 
> immediately executed, for pod2 recently created data is not available. )
> How we can commit the changes in synchronised manner.
>  
> *Code:*
> {code:java}
>  LeaseCheckMode leaseCheckMode = Boolean.TRUE.equals(enableLeaseCheck) ? 
> LeaseCheckMode.STRICT
> : LeaseCheckMode.DISABLED;
> documentNodeStore = new MongoDocumentNodeStoreBuilder()
> .setMongoDB(getMongoURI(), mongoDbName, 16)
> .setLeaseCheckMode(leaseCheckMode)
> .build();
>Repository repository = new Jcr(new 
> Oak(documentNodeStore)).createRepository();
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (OAK-10455) Synchronous commit

2023-09-25 Thread Nitul (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-10455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitul updated OAK-10455:

Summary: Synchronous commit  (was: synchronous commit)

> Synchronous commit
> --
>
> Key: OAK-10455
> URL: https://issues.apache.org/jira/browse/OAK-10455
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: commons
>Affects Versions: 1.48.0
>Reporter: Nitul
>Priority: Blocker
>
> We are using 1.48.0 version of oak-jcr. Out application stores the nodes and 
> retrive it.
> We are using multiple pods of this application. and consider below scenario 
> which is creating issue.
>  
> *Issue:*
> We have two request as below:
> Create some node and save it.- this is routed from pod1. (this will be saved 
> into mongo db after 1000ms with BackgroundUpdateOperation thread)
> Get created nodes - this is routed from pod2. (As this second request 
> immediately executed, for pod2 recently created data is not available. )
> How we can commit the changes in synchronised manner.
>  
> *Code:*
> {code:java}
>  LeaseCheckMode leaseCheckMode = Boolean.TRUE.equals(enableLeaseCheck) ? 
> LeaseCheckMode.STRICT
> : LeaseCheckMode.DISABLED;
> documentNodeStore = new MongoDocumentNodeStoreBuilder()
> .setMongoDB(getMongoURI(), mongoDbName, 16)
> .setLeaseCheckMode(leaseCheckMode)
> .build();
>Repository repository = new Jcr(new 
> Oak(documentNodeStore)).createRepository();
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)