patsonluk opened a new pull request, #2076:
URL: https://github.com/apache/solr/pull/2076
https://issues.apache.org/jira/browse/SOLR-17076
# Description
`OrderedNodePlacementPlugin#getAllReplicasOnNode` can be slow in a cluster
with lot of replicas. The effect could compoun
[
https://issues.apache.org/jira/browse/SOLR-17076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patson Luk updated SOLR-17076:
--
Summary: Replica Placement could be slow for new collection creation with
high amount of shards in a cl
[
https://issues.apache.org/jira/browse/SOLR-17076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patson Luk updated SOLR-17076:
--
Summary: Replica Placement could be slow for new collection creation with
high amount of shards in a cl
Patson Luk created SOLR-17076:
-
Summary: Replica Placement could be slow for new collection with
high amount of shard in a cluster with plenty replicas
Key: SOLR-17076
URL: https://issues.apache.org/jira/browse/SOLR-1
gerlowskija commented on code in PR #2072:
URL: https://github.com/apache/solr/pull/2072#discussion_r1393262795
##
solr/solr-ref-guide/modules/configuration-guide/pages/coreadmin-api.adoc:
##
@@ -349,9 +349,19 @@ This parameter is required in v1, and part of the url in
the v2 A
epugh commented on PR #2052:
URL: https://github.com/apache/solr/pull/2052#issuecomment-1810651483
> > Is the "startJettySolrRunner" method actually used? [...] I wonder if
that method is even needed???
>
> It's not used currently. I thought about deleting it, but wasn't sure
whether
pvcnt commented on code in PR #2071:
URL: https://github.com/apache/solr/pull/2071#discussion_r1392873965
##
solr/core/src/java/org/apache/solr/cluster/placement/plugins/AffinityPlacementFactory.java:
##
@@ -150,7 +150,7 @@ public AffinityPlacementConfig getConfig() {
* See
gerlowskija commented on PR #1681:
URL: https://github.com/apache/solr/pull/1681#issuecomment-1810571548
> In the package name?
I won't put words in his mouth, but I interpreted Anshum's comment as being
more about documentation and messaging around the client in general. As it
stan
pvcnt commented on PR #2071:
URL: https://github.com/apache/solr/pull/2071#issuecomment-1810514488
Sure, I was looking for feedback about the approach first! Since this looks
acceptable, I added some tests and documentation for the feature.
--
This is an automated message from the Apache
gerlowskija commented on PR #2052:
URL: https://github.com/apache/solr/pull/2052#issuecomment-1810509662
> Is the "startJettySolrRunner" method actually used? [...] I wonder if that
method is even needed???
It's not used currently. I thought about deleting it, but wasn't sure
whethe
[
https://issues.apache.org/jira/browse/SOLR-17075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17785941#comment-17785941
]
Eric Pugh commented on SOLR-17075:
--
Amazing how quickly the bit rot creeps in without th
HoustonPutman opened a new issue, #655:
URL: https://github.com/apache/solr-operator/issues/655
There are setups with kuberenetes that require logs to be written to a file,
so that they can then be uploaded to the log aggregators. Just logging to
stdout does not allow for this.
We do
Houston Putman created SOLR-17075:
-
Summary: Ref Guide link checking not enabled in "gradle check" by
default
Key: SOLR-17075
URL: https://issues.apache.org/jira/browse/SOLR-17075
Project: Solr
HoustonPutman opened a new pull request, #2075:
URL: https://github.com/apache/solr/pull/2075
(no comment)
--
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
dsmiley commented on PR #2071:
URL: https://github.com/apache/solr/pull/2071#issuecomment-1810385153
Looks good!
--
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 unsubscr
sigram commented on PR #85:
URL: https://github.com/apache/solr-sandbox/pull/85#issuecomment-1809926848
[This
documentation](https://kafka.apache.org/protocol.html#protocol_compatibility)
claims it's bi-directionally compatible, ie. old clients can talk with new
brokers and old brokers can
mkhludnev commented on PR #2074:
URL: https://github.com/apache/solr/pull/2074#issuecomment-1809866527
Thanks for approve @epugh. I'm thinking about test coverage. On top of my
head only a simple unittest with mocks. WDYT?
--
This is an automated message from the Apache Git Service.
To re
17 matches
Mail list logo
