entation and Refguide static HTML
> there so the webserver picks them up using an Alias. This no longer has
> anything to do with the CMS: The CMS bot is disabled and the whole CMS
> source folder also removed from SVN.
>
>
>
> If you would like to move that to another place in
Alias. This no longer has anything to do
>with the CMS: The CMS bot is disabled and the whole CMS source folder also
>removed from SVN.
If you would like to move that to another place in Subversion, let’s open an
Issue. But We need a place where to store huge number of files and res
Hi All,
(This email is BCC many (19) lists, please reply to bui...@apache.org only)
Infra has set a FINAL date of January 31st 2022 for the turn off of
ci.apache.org. This includes all of its nodes , of which the CMS node is
one. Therefore the CMS is also going to be gone on the 31st January
Hi Atri,
Congratulations again!
I'm not sure what your current situation is like.
ASF gives some guides for CMS.
https://www.apache.org/dev/cms.html
That page also includes a tutorial video link by Rob Weir.
https://www.youtube.com/watch?v=xcDZN3Lu6HA
And there is a reference page.
Hi All,
I am having trouble updating "Who We Are" page in adding my name using
the CMS. Could anyone point me to a tutorial/HOWTO I could use?
Regards,
Atri
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apac
ctargett closed pull request #644: SOLR-13394: Change default GC from CMS to G1
URL: https://github.com/apache/lucene-solr/pull/644
This is an automated message from the Apache Git Service.
To respond to the message, please
ctargett commented on issue #644: SOLR-13394: Change default GC from CMS to G1
URL: https://github.com/apache/lucene-solr/pull/644#issuecomment-501504613
Since SOLR-13394 is resolved as of 8.1, I assume this can be closed
namgyu
> Date: Mon Jun 3 17:55:47 2019
> New Revision: 1860573
>
> URL: http://svn.apache.org/viewvc?rev=1860573&view=rev
> Log:
> add Namgyu Kim in Lucene/Solr committer
>
> Modified:
> lucene/cms/trunk/content/whoweare.mdtext
>
> Modified: lucene/cms/trunk
l case, I think that parameter can really help performance ...
but some users will be seriously hampered by the lack of working Java
commandline tools. Whether or not we leave it in by default, some
documentation is a good idea.
> Change default GC fr
but document it better. It would be nice to have an
option in {{bin/solr}} to easily turn it off for development, eg. {{bin/solr
-debug}}
> Change default GC from CMS to G1
>
>
> Key: SOLR-13394
> URL: https://issues.apa
lack, the -XX:+PerfDisableSharedMem causes the Solr
process to not show up in the `jps` output. Some details about this parameter
is here: https://www.evanjones.ca/jvm-mmap-pause.html
Does someone think that this warrants a revert of that parameter?
> Change default GC from CM
mmit 6797274581e3f01979f54598aeee533b22cc5d74 in lucene-solr's branch
refs/heads/branch_8x from Ishan Chattopadhyaya
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=6797274 ]
SOLR-13394: Updating contributors for this issue in CHANGES.txt
> Change default GC fr
mmit 560b5e779d469dd5219a633fbeb09fd064174b74 in lucene-solr's branch
refs/heads/master from Ishan Chattopadhyaya
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=560b5e7 ]
SOLR-13394: Updating contributors for this issue in CHANGES.txt
> Change default GC fr
mmit a15ad1729e34c06c6e6639900fdadd39bd35c6a6 in lucene-solr's branch
refs/heads/branch_8_1 from Ishan Chattopadhyaya
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=a15ad17 ]
SOLR-13394: Updating contributors for this issue in CHANGES.txt
> Change default GC fr
mmit 5cb3f23f55deb7e5ecd8f9c75d25be8e5b5a7099 in lucene-solr's branch
refs/heads/branch_8_1 from Ishan Chattopadhyaya
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=5cb3f23 ]
SOLR-13394: Tweaking G1 parameters and adding ref guide documentation
> Change default GC fr
mmit ac2e1e3cea8eae3a81a1af16eaece81bbb37695b in lucene-solr's branch
refs/heads/branch_8x from Ishan Chattopadhyaya
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=ac2e1e3 ]
SOLR-13394: Tweaking G1 parameters and adding ref guide documentation
> Change default GC fr
mmit 91969f40fe1db83f7c5d93d3fa693fe282e17ae9 in lucene-solr's branch
refs/heads/master from Ishan Chattopadhyaya
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=91969f4 ]
SOLR-13394: Tweaking G1 parameters and adding ref guide documentation
> Change default GC fr
Change default GC from CMS to G1
>
>
> Key: SOLR-13394
> URL: https://issues.apache.org/jira/browse/SOLR-13394
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Defaul
[
https://issues.apache.org/jira/browse/SOLR-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kesharee Nandan Vishwakarma updated SOLR-13394:
---
Attachment: SOLR-13394.patch
> Change default GC from CMS to
that sounds good. Adding a patch with the same.
> Change default GC from CMS to G1
>
>
> Key: SOLR-13394
> URL: https://issues.apache.org/jira/browse/SOLR-13394
> Project: Solr
> Issue Type: Im
. Does that sound reasonable?
> Change default GC from CMS to G1
>
>
> Key: SOLR-13394
> URL: https://issues.apache.org/jira/browse/SOLR-13394
> Project: Solr
> Issue Type: Improvement
> S
3394:
[~ichattopadhyaya] Can we add Notes regarding default region size and some
other G1 options Somewhere in scripts or README?
Also we can to specify for which heap size range, these settings are
recommended.
> Change default GC from CMS to G1
>
>
>
ning, that at least
mentions the region size parameter.
> Change default GC from CMS to G1
>
>
> Key: SOLR-13394
> URL: https://issues.apache.org/jira/browse/SOLR-13394
> Project: Solr
>
e GC type dynamically based
on -Xmx or -Xms settings?
> Change default GC from CMS to G1
>
>
> Key: SOLR-13394
> URL: https://issues.apache.org/jira/browse/SOLR-13394
> Project: Solr
> Issue Type: Imp
ting and let G1 choose the default.
# {{-XX:InitiatingHeapOccupancyPercent=45}} is redundant because the default is
already 45.
# Also if we are going to enable large pages, then adding
{{-XX:+AlwaysPreTouch}} is also a good idea to move the defrag costs to startup.
> Change default GC from CM
yaya - Was this supposed to be changed on the 8.x branch or
just on master (9.x) where the switch to JDK 11 was made?
I intended this for Solr 8.1 (Java 8+). Do you suggest otherwise and restrict
to 9x?
> Change default GC from CMS to G1
>
>
>
o be changed on the 8.x branch or just
on master (9.x) where the switch to JDK 11 was made?
> Change default GC from CMS to G1
>
>
> Key: SOLR-13394
> URL: https://issues.apache.org/jira/browse/SOLR-13394
>
risdenk commented on issue #644: SOLR-13394: Change default GC from CMS to G1
URL: https://github.com/apache/lucene-solr/pull/644#issuecomment-487065342
@chatman - I think this PR can be closed?
This is an automated message
@lucene.apache.org
Subject: Re: svn commit: r1858076 - /lucene/cms/trunk/templates/sidenav.mdtext
Uwe,
See my previous email two days ago with title "Fix license link on project
website", see https://www.apache.org/foundation/marks/pmcs#navigation
But I think this requireme
we
>
> -
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> https://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>> -Original Message-
>> From: jan...@apache.org
>> Sent: Wednesday, April 24, 2019 11:55 PM
>> To: comm...@lucene.apache.org
>
: 8.1
Thanks [~keshareenv], [~erickerickson], [~thetaphi], [~elyograg].
Congratulations [~keshareenv] for your first, one of many contributions to come.
> Change default GC from CMS to G1
>
>
> Key: SOLR-13394
>
mmit 430f0593805168a3e7abdbfa535528f5584d476a in lucene-solr's branch
refs/heads/branch_8x from Ishan Chattopadhyaya
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=430f059 ]
SOLR-13394: Switch default GC from CMS to G1
> Change default GC fr
mmit 9c77889217fa6cb3c4f95a76552895496851d200 in lucene-solr's branch
refs/heads/master from Ishan Chattopadhyaya
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=9c77889 ]
SOLR-13394: Switch default GC from CMS to G1
> Change default GC fr
?
Uwe
-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: jan...@apache.org
> Sent: Wednesday, April 24, 2019 11:55 PM
> To: comm...@lucene.apache.org
> Subject: svn commit: r1858076 -
> /lu
able ... but I could be wrong!
If that option is deprecated, then there would be no reason to keep it.
> Change default GC from CMS to G1
>
>
> Key: SOLR-13394
> URL: https://issues.apache.org/jira/browse/SOLR-1339
oved AggressiveOpts, since this has been deprecated in Java 11 and removed
in later releases. [~thetaphi] Nice catch :)
[~ichattopadhyaya] I have added upgrade notes for this.
> Change default GC from CMS to G1
>
>
> Key: SOLR-13394
>
[
https://issues.apache.org/jira/browse/SOLR-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kesharee Nandan Vishwakarma updated SOLR-13394:
---
Attachment: (was: SOLR-13394.patch)
> Change default GC from
[
https://issues.apache.org/jira/browse/SOLR-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kesharee Nandan Vishwakarma updated SOLR-13394:
---
Attachment: SOLR-13394.patch
> Change default GC from CMS to
kesharee commented on a change in pull request #644: SOLR-13394: Change default
GC from CMS to G1
URL: https://github.com/apache/lucene-solr/pull/644#discussion_r276788540
##
File path: solr/bin/solr.cmd
##
@@ -1167,20 +1167,14 @@ set SOLR_OPTS=%SOLR_JAVA_STACK_SIZE
Opts}}, really!
> Change default GC from CMS to G1
>
>
> Key: SOLR-13394
> URL: https://issues.apache.org/jira/browse/SOLR-13394
> Project: Solr
> Issue Type: Improvement
> Security Le
uschindler commented on a change in pull request #644: SOLR-13394: Change
default GC from CMS to G1
URL: https://github.com/apache/lucene-solr/pull/644#discussion_r276282835
##
File path: solr/bin/solr.cmd
##
@@ -1167,20 +1167,14 @@ set SOLR_OPTS=%SOLR_JAVA_STACK_SIZE
the patch. Settings look good to me; these seem to be
based on Shawn Heisey's wiki page.
Can you please also update the Upgrade Notes section of the solr/CHANGES.txt
with the information that users need to take notice?
> Change default GC fr
kesharee opened a new pull request #644: SOLR-13394: Change default GC from CMS
to G1
URL: https://github.com/apache/lucene-solr/pull/644
This is an automated message from the Apache Git Service.
To respond to the message
[
https://issues.apache.org/jira/browse/SOLR-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kesharee Nandan Vishwakarma updated SOLR-13394:
---
Attachment: SOLR-13394.patch
> Change default GC from CMS to
[
https://issues.apache.org/jira/browse/SOLR-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kesharee Nandan Vishwakarma updated SOLR-13394:
---
Attachment: (was: SOLR-13394.patch)
> Change default GC from
[
https://issues.apache.org/jira/browse/SOLR-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kesharee Nandan Vishwakarma updated SOLR-13394:
---
Attachment: SOLR-13394.patch
> Change default GC from CMS to
the field using G1.
> Change default GC from CMS to G1
>
>
> Key: SOLR-13394
> URL: https://issues.apache.org/jira/browse/SOLR-13394
> Project: Solr
> Issue Type: Improvement
> Se
with doing this?
> Change default GC from CMS to G1
>
>
> Key: SOLR-13394
> URL: https://issues.apache.org/jira/browse/SOLR-13394
> Project: Solr
> Issue Type: Improvement
> Security Le
Ishan Chattopadhyaya created SOLR-13394:
---
Summary: Change default GC from CMS to G1
Key: SOLR-13394
URL: https://issues.apache.org/jira/browse/SOLR-13394
Project: Solr
Issue Type
mmit 80f5162c85012292d50aba0b2b54fa2bd109107b in lucene-solr's branch
refs/heads/branch_7_3 from [~shalinmangar]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=80f5162 ]
SOLR-12098: Document the Lucene spins auto-detection and its effect on CMS
dynamic defaults
(cherry pi
!
> Document the Lucene spins auto-detection and its effect on CMS dynamic
> defaults
> ---
>
> Key: SOLR-12098
> URL: https://issues.apache.org/jira/browse/SOLR-12098
>
mmit d50890e92541233cbdedf6d557e5b8b4554660ca in lucene-solr's branch
refs/heads/master from [~shalinmangar]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d50890e ]
SOLR-12098: Document the Lucene spins auto-detection and its effect on CMS
dynamic defaults
> Document the
mmit ad82d65a7a9482e11bc56f18b7ec3c5833583fcf in lucene-solr's branch
refs/heads/branch_7x from [~shalinmangar]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=ad82d65 ]
SOLR-12098: Document the Lucene spins auto-detection and its effect on CMS
dynamic defaults
(cherry picked fr
uple really minor typos in your patch (a
missing period, heading capitalization). +1 to commit when you're ready. Thanks
> Document the Lucene spins auto-detection and its effect on CMS dynamic
on CMS dynamic
> defaults
> ---
>
> Key: SOLR-12098
> URL: https://issues.apache.org/jira/browse/SOLR-12098
> Project: Solr
> Issue Type: Task
>
ther it's not the time to make SSDs the default.
+1, I'll open an issue.
> Document the Lucene spins auto-detection and its effect on CMS dynamic
> defaults
> ---
>
> Key: SOLR-12098
the Indexconfig in Solrconfig and Taking Solr to Production
pages and adds information about this property and its effects.
> Document the Lucene spins auto-detection and its effect on CMS dynamic
>
its effect on CMS dynamic
> defaults
> ---
>
> Key: SOLR-12098
> URL: https://issues.apache.org/jira/browse/SOLR-12098
> Project: Solr
> Issue Type: Ta
ument the Lucene spins auto-detection and its effect on CMS dynamic
> defaults
> ---
>
> Key: SOLR-12098
> URL: https://issues.apache.org/jira/browse/SOLR-12098
>
Shalin Shekhar Mangar created SOLR-12098:
Summary: Document the Lucene spins auto-detection and its effect
on CMS dynamic defaults
Key: SOLR-12098
URL: https://issues.apache.org/jira/browse/SOLR-12098
e to the ASF CMS
> ---
>
> Key: SOLR-5985
> URL: https://issues.apache.org/jira/browse/SOLR-5985
> Project: Solr
> Issue Type: Task
> Components: docume
e "content/latestversion.mdtext" %} Demo
: Date: Tue, 15 Dec 2015 08:25:20 -
: From: ans...@apache.org
: Reply-To: dev@lucene.apache.org
: To: comm...@lucene.apache.org
: Subject: svn commit: r1720085 -
: /lucene/cms/trunk/content/core/quickstart.mdtext
:
: Author: anshum
: Date: Tue
Ah; I see you fixed it already. Thanks!
On Thu, Jul 2, 2015 at 7:18 PM david.w.smi...@gmail.com <
david.w.smi...@gmail.com> wrote:
> Palm-to-face! I'll fix later today.
> On Thu, Jul 2, 2015 at 5:29 PM Chris Hostetter
> wrote:
>
>>
>> Ummm, david ... i hate to tell you this, but it looks like y
Palm-to-face! I'll fix later today.
On Thu, Jul 2, 2015 at 5:29 PM Chris Hostetter
wrote:
>
> Ummm, david ... i hate to tell you this, but it looks like you forgot the
> "L" in "Solr" in the title of your own book.
>
> more then once.
>
> :)
>
> : Mitchell](https://www.linkedin.com/in/mat
Ummm, david ... i hate to tell you this, but it looks like you forgot the
"L" in "Solr" in the title of your own book.
more then once.
:)
: Mitchell](https://www.linkedin.com/in/mattmitchell4) are proud to
: *finally* announce the book â??[Apache Sor Enterprise Search Server,
...
:
and at least then the search button->box feature worked correctly.
>>
>>
>>
>> : Date: Fri, 13 Feb 2015 10:35:13 -
>> : From: jan...@apache.org
>> : Reply-To: dev@lucene.apache.org
>> : To: comm...@lucene.apache.org
>> : Subject: svn commit: r1
g anything
> and at least then the search button->box feature worked correctly.
>
>
>
> : Date: Fri, 13 Feb 2015 10:35:13 -
> : From: jan...@apache.org
> : Reply-To: dev@lucene.apache.org
> : To: comm...@lucene.apache.org
> : Subject: svn commit: r1659492 - /l
0
: From: jan...@apache.org
: Reply-To: dev@lucene.apache.org
: To: comm...@lucene.apache.org
: Subject: svn commit: r1659492 - /lucene/cms/trunk/templates/_solr-head.html
:
: Author: janhoy
: Date: Fri Feb 13 10:35:13 2015
: New Revision: 1659492
:
: URL: http://svn.apache.org/r1659492
: Log:
:
On 2/7/2015 10:30 AM, Shawn Heisey wrote:
> Lastly, CMS itself could be modified to severely throttle the incoming
> thread rather than completely stall it. If the throttled rate were high
> enough to ensure that the JDBC connection saw activity at least once
> every 15 seconds, t
While reviewing recent changes to the Solr Reference Guide, I came
across a mention of LUCENE-6063, which I hadn't noticed before.
https://issues.apache.org/jira/browse/LUCENE-6063
People using Solr's dataimport handler sometimes run into a show-stopper
problem with the CMS denial-
tly always set CMS values in LuceneTestCase.newIndexWriterConfig
> ---
>
> Key: LUCENE-6122
> URL: https://issues.apache.org/jira/browse/LUCENE-6122
> Project: Lucene - Cor
6122:
-
Commit 1646853 from [~mikemccand] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1646853 ]
LUCENE-6122: always set CMS settings in LuceneTestCase.newIndexWriterConfig
> explicitly always set CMS values in LuceneTestCase.new
6122:
-
Commit 1646850 from [~mikemccand] in branch 'dev/trunk'
[ https://svn.apache.org/r1646850 ]
LUCENE-6122: always set CMS settings in LuceneTestCase.newIndexWriterConfig
> explicitly always set CMS values in LuceneTestCase.new
sing CMS
> explicitly always set CMS values in LuceneTestCase.newIndexWriterConfig
> ---
>
> Key: LUCENE-6122
> URL: https://issues.apache.org/jira/browse/LUCENE-6122
>
[
https://issues.apache.org/jira/browse/LUCENE-6122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-6122:
---
Attachment: LUCENE-6122.patch
Simple patch...
> explicitly always set CMS values
Robert Muir created LUCENE-6122:
---
Summary: explicitly always set CMS values in
LuceneTestCase.newIndexWriterConfig
Key: LUCENE-6122
URL: https://issues.apache.org/jira/browse/LUCENE-6122
Project
hen CMS has stalled threads
> -
>
> Key: LUCENE-6094
> URL: https://issues.apache.org/jira/browse/LUCENE-6094
> Project: Lucene - Core
> Issue Type: Bug
>
6094:
-
Commit 1643769 from [~mikemccand] in branch 'dev/branches/lucene_solr_4_10'
[ https://svn.apache.org/r1643769 ]
LUCENE-6094: allow IW.rollback to stop CMS's stalling too
> IW.rollback can take forever when C
[
https://issues.apache.org/jira/browse/LUCENE-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reopened LUCENE-6094:
Reopen for 4.10.3 backport
> IW.rollback can take forever when CMS has stal
[
https://issues.apache.org/jira/browse/LUCENE-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-6094.
Resolution: Fixed
> IW.rollback can take forever when CMS has stalled thre
6094:
-
Commit 1643509 from [~mikemccand] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1643509 ]
LUCENE-6094: allow IW.rollback to stop CMS's stalling too
> IW.rollback can take forever when C
6094:
-
Commit 1643508 from [~mikemccand] in branch 'dev/trunk'
[ https://svn.apache.org/r1643508 ]
LUCENE-6094: allow IW.rollback to stop CMS's stalling too
> IW.rollback can take forever when CMS has stalled threads
> -
>
&
[
https://issues.apache.org/jira/browse/LUCENE-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236508#comment-14236508
]
Robert Muir commented on LUCENE-6094:
-
+1
> IW.rollback can take forever w
s w/o the fix ...
> IW.rollback can take forever when CMS has stalled threads
> -
>
> Key: LUCENE-6094
> URL: https://issues.apache.org/jira/browse/LUCENE-6094
> Project: Lucene
Michael McCandless created LUCENE-6094:
--
Summary: IW.rollback can take forever when CMS has stalled threads
Key: LUCENE-6094
URL: https://issues.apache.org/jira/browse/LUCENE-6094
Project: Lucene
Clone URL (Committers only):
https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://lucene.apache.org/solr%2Fbooks.mdtext
Mathieu
Index: trunk/content/solr/books.mdtext
===
--- trunk/content/solr/books.mdtext (revis
t be if our website was that minimal.
> Consider moving the Solr Reference Guide from Confluence to the ASF CMS
> ---
>
> Key: SOLR-5985
> URL: https://issues.apache.org/ji
Steve Rowe created SOLR-5985:
Summary: Consider moving the Solr Reference Guide from Confluence
to the ASF CMS
Key: SOLR-5985
URL: https://issues.apache.org/jira/browse/SOLR-5985
Project: Solr
5, 2013, at 1:03 PM, Steve Rowe wrote:
>>
>>> Unfortunately, the 4.6 Solr Ref Guide hasn’t been released yet, so
>>> solrnews.mdtext is wrong - I’ll fix:
>>>
>>> On Nov 24, 2013, at 1:39 PM, sim...@apache.org wrote:
>>> […]
>>>> Modified: lucene
ws.mdtext is wrong - I’ll fix:
>>
>> On Nov 24, 2013, at 1:39 PM, sim...@apache.org wrote:
>> […]
>>> Modified: lucene/cms/trunk/content/solr/solrnews.mdtext
>>> URL:
>>> http://svn.apache.org/viewvc/lucene/cms/trun
Fixed.
On Nov 25, 2013, at 1:03 PM, Steve Rowe wrote:
> Unfortunately, the 4.6 Solr Ref Guide hasn’t been released yet, so
> solrnews.mdtext is wrong - I’ll fix:
>
> On Nov 24, 2013, at 1:39 PM, sim...@apache.org wrote:
> […]
>> Modified: lucene/cms/trunk/content/solr/s
Unfortunately, the 4.6 Solr Ref Guide hasn’t been released yet, so
solrnews.mdtext is wrong - I’ll fix:
On Nov 24, 2013, at 1:39 PM, sim...@apache.org wrote:
[…]
> Modified: lucene/cms/trunk/content/solr/solrnews.mdtext
> URL:
> http://svn.apache.org/viewvc/lucene/cms/trunk/con
Rob!
> CMS setters cannot work unless you setMaxMergeCount before you
> setMaxThreadCount
>
>
> Key: LUCENE-5080
> URL: https://issues.apache.org/jira/browse/LUCENE-5080
. If someone is unhappy about the name, i won't be
offended, we can change it.
At least jenkins will have a nice weekend in the meantime.
> CMS setters cannot work unless you setMaxMergeCount before you
> setMax
with
reflection.
> CMS setters cannot work unless you setMaxMergeCount before you
> setMaxThreadCount
>
>
> Key: LUCENE-5080
> URL: https://issues.apac
ed the two setters
into one and didnt do any ctors (that would sorta be redundant with the
combined-setter, and i dont like the name reset).
Additionally i made the defaults public constants.
> CMS setters cannot work unless you setMaxMergeCount before you
> s
eset(int,int) to avoid that case?
{quote}
Fine by me. if we decide we dont like it later, we can just remove it.
> CMS setters cannot work unless you setMaxMergeCount before you
> setMaxT
may want to dynamically set that based
on some overall application workload. Since MS is on LiveIWC, it's fine cause
you can reset to a new CMS instance. But in that case what will happen to the
other CMS which loops until IW has no more merges? Is that ok?
Maybe instead we can have CMS.rese
[
https://issues.apache.org/jira/browse/LUCENE-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694841#comment-13694841
]
Michael McCandless commented on LUCENE-5080:
+1
&
Robert Muir created LUCENE-5080:
---
Summary: CMS setters cannot work unless you setMaxMergeCount
before you setMaxThreadCount
Key: LUCENE-5080
URL: https://issues.apache.org/jira/browse/LUCENE-5080
1 - 100 of 221 matches
Mail list logo
