[
https://issues.apache.org/jira/browse/SOLR-9139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Mani updated SOLR-9139:
----------------------------
Description:
ReplicationHandler has volatile class member snapShootDetails.
The variable is not reset on new submission.
Usecase:
On Core1 running a JVM1, submit a replication request.
I poll this thread to check the replication status invoking the handler passing
"command=details".
Issue:
I submit request1 on core1 to create replication. Poll the status using
details.
Once the replication is complete, i submit the replication request2 on core1
again. When when we poll using handler for replication details, it still has
request1 details.
I think on new submission, the previous request details(request1 in this eg)
should be reset (meaning snapshotdetails= null) on new request.
The getDetails should be returned the status of request2 instead of request1
details. This doesn't happen untill request2 either succeeds or fails.
was:
ReplicationHandler has volatile class member snapShootDetails.
The variable is not reset on new submission.
Usecase:
On Core1 running a JVM1, submit a replication request.
I poll this thread to check the replication status invoking the handler passing
"command=details".
Issue:
I submit request1 on core1 to create replication. Poll the status using
details.
Once the replication is complete, i submit the replication request2 on core1
again. When when we poll using handler for replication details, it still has
request1 details.
I think on new submission, the previous request details(request1 in this eg)
should be reset (meaning snapshotdetails= null) on new request.
We don't have to wait till the request2 snapshot completes.
> ReplicationHandler getReplicationDetails() returns previous replicationData
> ---------------------------------------------------------------------------
>
> Key: SOLR-9139
> URL: https://issues.apache.org/jira/browse/SOLR-9139
> Project: Solr
> Issue Type: Bug
> Components: replication (java)
> Affects Versions: 5.5
> Reporter: Arun Mani
> Priority: Minor
>
> ReplicationHandler has volatile class member snapShootDetails.
> The variable is not reset on new submission.
> Usecase:
> On Core1 running a JVM1, submit a replication request.
> I poll this thread to check the replication status invoking the handler
> passing "command=details".
> Issue:
> I submit request1 on core1 to create replication. Poll the status using
> details.
> Once the replication is complete, i submit the replication request2 on core1
> again. When when we poll using handler for replication details, it still has
> request1 details.
> I think on new submission, the previous request details(request1 in this eg)
> should be reset (meaning snapshotdetails= null) on new request.
> The getDetails should be returned the status of request2 instead of request1
> details. This doesn't happen untill request2 either succeeds or fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
