sonatype-lift[bot] commented on code in PR #1757:
URL: https://github.com/apache/solr/pull/1757#discussion_r1254670436
##########
solr/core/src/java/org/apache/solr/servlet/CoordinatorHttpSolrCall.java:
##########
@@ -152,15 +143,13 @@ private static void setMDCLoggingContext(String
collectionName) {
private static void addReplica(String syntheticCollectionName, CoreContainer
cores) {
SolrQueryResponse rsp = new SolrQueryResponse();
try {
+ CollectionAdminRequest.AddReplica addReplicaRequest =
+ CollectionAdminRequest.addReplicaToShard(syntheticCollectionName,
"shard1")
+ .setCreateNodeSet(cores.getZkController().getNodeName());
+ addReplicaRequest.setWaitForFinalState(true);
cores
.getCollectionsHandler()
- .handleRequestBody(
- new LocalSolrQueryRequest(
- null,
-
CollectionAdminRequest.addReplicaToShard(syntheticCollectionName, "shard1")
- .setCreateNodeSet(cores.getZkController().getNodeName())
- .getParams()),
- rsp);
+ .handleRequestBody(new LocalSolrQueryRequest(null,
addReplicaRequest.getParams()), rsp);
Review Comment:
<picture><img alt="14% of developers fix this issue"
src="https://lift.sonatype.com/api/commentimage/fixrate/14/display.svg"></picture>
<b>*RESOURCE_LEAK:</b>* resource of type
`org.apache.solr.request.LocalSolrQueryRequest` acquired by call to
`LocalSolrQueryRequest(...)` at line 152 is not released after line 152.
**Note**: potential exception at line 152
---
<details><summary>ℹ️ Expand to see all <b>@sonatype-lift</b>
commands</summary>
You can reply with the following commands. For example, reply with
***@sonatype-lift ignoreall*** to leave out all findings.
| **Command** | **Usage** |
| ------------- | ------------- |
| `@sonatype-lift ignore` | Leave out the above finding from this PR |
| `@sonatype-lift ignoreall` | Leave out all the existing findings from this
PR |
| `@sonatype-lift exclude <file\|issue\|path\|tool>` | Exclude specified
`file\|issue\|path\|tool` from Lift findings by updating your config.toml file |
**Note:** When talking to LiftBot, you need to **refresh** the page to see
its response.
<sub>[Click here](https://github.com/apps/sonatype-lift/installations/new)
to add LiftBot to another repo.</sub></details>
##########
solr/core/src/java/org/apache/solr/servlet/CoordinatorHttpSolrCall.java:
##########
@@ -127,7 +111,14 @@ public static SolrCore getCore(
}
addReplica(syntheticCollectionName, solrCall.cores);
- core = solrCall.getCoreByCollection(syntheticCollectionName,
isPreferLeader);
+ }
+ core = solrCall.getCoreByCollection(syntheticCollectionName,
isPreferLeader);
Review Comment:
<picture><img alt="7% of developers fix this issue"
src="https://lift.sonatype.com/api/commentimage/fixrate/7/display.svg"></picture>
<b>*THREAD_SAFETY_VIOLATION:</b>* Read/Write race. Non-private method
`CoordinatorHttpSolrCall.getCore(...)` indirectly reads without synchronization
from container `core.SolrResourceLoader.classNameCache` via call to
`Map.get(...)`. Potentially races with write in method
`CoordinatorHttpSolrCall.getCoreByCollection(...)`.
Reporting because a superclass `class org.apache.solr.servlet.HttpSolrCall`
is annotated `@ThreadSafe`, so we assume that this method can run in parallel
with other non-private methods in the class (including itself).
---
<details><summary>ℹ️ Expand to see all <b>@sonatype-lift</b>
commands</summary>
You can reply with the following commands. For example, reply with
***@sonatype-lift ignoreall*** to leave out all findings.
| **Command** | **Usage** |
| ------------- | ------------- |
| `@sonatype-lift ignore` | Leave out the above finding from this PR |
| `@sonatype-lift ignoreall` | Leave out all the existing findings from this
PR |
| `@sonatype-lift exclude <file\|issue\|path\|tool>` | Exclude specified
`file\|issue\|path\|tool` from Lift findings by updating your config.toml file |
**Note:** When talking to LiftBot, you need to **refresh** the page to see
its response.
<sub>[Click here](https://github.com/apps/sonatype-lift/installations/new)
to add LiftBot to another repo.</sub></details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]