[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527113#comment-13527113 ] Markus Jelsma commented on SOLR-4030: - Why did you mark this as `not a problem`. This issue is not resolved. Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Radim Kolar Priority: Minor Labels: patch Fix For: 4.1, 5.0 add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527135#comment-13527135 ] Radim Kolar commented on SOLR-4030: --- It was resolved for me. If you need this open your ticket. Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Radim Kolar Priority: Minor Labels: patch Fix For: 4.1, 5.0 add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527176#comment-13527176 ] Michael McCandless commented on SOLR-4030: -- Radim, maybe you can put your patch back? Other users could apply it / improve it, someone else may add a test case, etc., and it will eventually be committed. The process takes time ... Until Solr catches up, users can also look at ElasticSearch ... it's had IO throttling for a while now ( https://github.com/elasticsearch/elasticsearch/issues/2041 ) Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Radim Kolar Priority: Minor Labels: patch Fix For: 4.1, 5.0 add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527181#comment-13527181 ] Radim Kolar commented on SOLR-4030: --- You guys had 1 month of time and wasted it. Now we fork and taking our patches with us. Case closed. Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Radim Kolar Priority: Minor Labels: patch Fix For: 4.1, 5.0 add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527187#comment-13527187 ] Jack Krupansky commented on SOLR-4030: -- bq. Now we fork Forking is understandable when you have time pressure and other interests to satisfy. No problem there. Hopefully you can contribute back some of the work from your fork. bq. taking our patches with us. How is that related to forking? I mean, sure, you can apply the patch on your own fork, but why does forking imply that you think you need to delete the posted patch? Besides, didn't you cede ownership of the patch to the community/ASF when you posted it? So, technically, it is no longer yours, right? It sounds like you need a refresher course in Community 101! Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Radim Kolar Priority: Minor Labels: patch Fix For: 4.1, 5.0 add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: [jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
Jack, yes re ownership. Mind opening an issue and reattaching? I saw this was done to 2 issues. Thanks! Otis -- SOLR Performance Monitoring - http://sematext.com/spm On Dec 8, 2012 11:31 AM, Jack Krupansky (JIRA) j...@apache.org wrote: [ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527187#comment-13527187] Jack Krupansky commented on SOLR-4030: -- bq. Now we fork Forking is understandable when you have time pressure and other interests to satisfy. No problem there. Hopefully you can contribute back some of the work from your fork. bq. taking our patches with us. How is that related to forking? I mean, sure, you can apply the patch on your own fork, but why does forking imply that you think you need to delete the posted patch? Besides, didn't you cede ownership of the patch to the community/ASF when you posted it? So, technically, it is no longer yours, right? It sounds like you need a refresher course in Community 101! Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Radim Kolar Priority: Minor Labels: patch Fix For: 4.1, 5.0 add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527223#comment-13527223 ] Radim Kolar commented on SOLR-4030: --- Unless you have written permission from us to distribute our work, you are losing court case against us after we prove to court that we are authors of code in question. We never lost such cases. Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Radim Kolar Priority: Minor Labels: patch Fix For: 4.1, 5.0 add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527224#comment-13527224 ] Uwe Schindler commented on SOLR-4030: - I will contact the board about what's going on here. Unfortunately, the custom JIRA plugin where you had to sign the ASF contribution by clicking the checkbox is no longer working with JIRA 5.2, now used by this server. Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Radim Kolar Priority: Minor Labels: patch Fix For: 4.1, 5.0 add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527227#comment-13527227 ] Markus Jelsma commented on SOLR-4030: - We've had the same issues with him at Apache Nutch. After contacting the board it was decided to restore the original patch but not include it in the source tree, and ignore it further. Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Radim Kolar Priority: Minor Labels: patch Fix For: 4.1, 5.0 add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527228#comment-13527228 ] Mark Miller commented on SOLR-4030: --- Apache has a pretty clear record in these cases I think - if a contributor wishes to withdraw his own work - especially if it's not yet committed to the codebase - we should simply allow them to do so. I'm sure situations around this can get complicated, but this case does not seem complicated at all. These patches have only one author and they have not been committed yet. We are in the business of accepting patches from *willing* contributors. If someone wants to see these features implemented, I'd suggested writing new patches. Neither issue is very large. Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Radim Kolar Priority: Minor Labels: patch Fix For: 4.1, 5.0 add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527230#comment-13527230 ] Uwe Schindler commented on SOLR-4030: - Thanks Markus. So restoring patches in JIRA actually works with help of infra, but this is useless here, as we would not use it in our source tree. And: He said it is trivial, so anybody who has interest in this functionality could write the code easily. So I see no problem and we just leave the issue open until somebody has the time to resolve this with a good patch. I think we should ignore Radim for any patches about Lucene and Solr, his social competence seems to be zero. I added a filter to my mail inbox. Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Radim Kolar Priority: Minor Labels: patch Fix For: 4.1, 5.0 add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527232#comment-13527232 ] Jack Krupansky commented on SOLR-4030: -- bq. if a contributor wishes to withdraw his own work - especially if it's not yet committed to the codebase - we should simply allow them to do so. That makes sense at least for a short interval, except for the case of anyone who may have included the patch in their own fork and maybe even could be in production with it and is now in limbo or worse. In this specific instance the triviality and brief tenure of the patch kind of makes it moot, but for future instances now we have to think twice when recommending a non-committed patch. At a minimum, somewhere there needs to be a notice/warning that use and ownership of uncommitted patches is a potentially questionable and risky activity - and that permisssion can be revoked at any moment. And if the donate check box can't be restored, then there needs to be some mechanism for a donor to explicitly cede ownership, to at least confirm the donation even if its legal status may vary from jurisdiction to jurisdiction. Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Radim Kolar Priority: Minor Labels: patch Fix For: 4.1, 5.0 add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527238#comment-13527238 ] Yonik Seeley commented on SOLR-4030: Lets not over-think this or make it too complicated guys... No, you can't take back a contribution once it's been contributed. If/when it's been committed or not is just a detail. We can normally *choose* not to commit it (the distinction is pretty important), and I think that's what we should do here. If a contribution wasn't valid in the first place (i.e. someone saying... hey, this person didn't have permission to contribute X) then we can figure that out on a case-by-case basis. Hasn't happened yet here AFAIK. Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Unassigned Developer Priority: Minor Labels: patch Fix For: 4.1, 5.0 add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527242#comment-13527242 ] Uwe Schindler commented on SOLR-4030: - @Yonik: I agree here, we should not overcomplicate it. Just ignore Radim (at least I will do this). My only problem here is the missing checkbox in JIRA, where the users from the beginning have to specify if they agree with the Apache License. In that case, Radim would not be able to go to court or think about it, because he agreed on publishing the patch by open source terms. The problem, as Jack now explain, is the case for external people, using this issue tracker as a source for their work. Maybe some company would have used Radim's patch for their own product! Nobody inform them that he removed his patch here. In my opinion, you should not be able to at least remove patches in JIRA, but just offer the option to say at a later stage: I submitted the patch, but I need to undo that. This should be noted in the submit form, so anybody who is not sure if the patch can be added here, would not do it. If some patch really have to be deleted, only PMC members should be able to do this completely (like in SVN where you can revert, but you have no chance to completely remove the occurence - only SVN admins could really remove a commit completely). To stop Radim editing this issues or reopen/close it, I set a new reporter. Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Lucene Developers Priority: Minor Labels: patch Fix For: 4.1, 5.0 add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527244#comment-13527244 ] Yonik Seeley commented on SOLR-4030: The checkbox was never necessary - it's just that people became used to seeing it and started assuming it was. Contributions to our software are under the ASL by default - one would need to explicitly state when adding something that looks like a contribution to our JIRA that it was in fact *not* a contribution (and that is what the old checkbox facilitated). Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Lucene Developers Priority: Minor Labels: patch Fix For: 4.1, 5.0 add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527247#comment-13527247 ] Uwe Schindler commented on SOLR-4030: - bq. Contributions to our software are under the ASL by default But does any user who opens an issue knows this? The Apache Issue tracker is missing a extra page, referred from the create issue / upload patch page that all work done here is under ASL. My own issue tracker presents the terms and conditions to the user when using the issue tracker. Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Lucene Developers Priority: Minor Labels: patch Fix For: 4.1, 5.0 add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527260#comment-13527260 ] Radim Kolar commented on SOLR-4030: --- Yes, i had similar issue with nutch project. Markus Jelsma reuploaded my patch back to JIRA and refused to delete it. Its still in JIRA violating my copyright laws. I decided not to escalate the conflict and go after ASF and harm other projects just because of misbehavior of one person. Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Lucene Developers Priority: Minor Labels: patch Fix For: 4.1, 5.0 add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527288#comment-13527288 ] Erick Erickson commented on SOLR-4030: -- Radim: At some point, you might reflect upon the fact that the common element in your conflicts with various Apache projects is...you. Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Lucene Developers Priority: Minor Labels: patch Fix For: 4.1, 5.0 add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13508813#comment-13508813 ] Radim Kolar commented on SOLR-4030: --- any progress on this? its trivial patch. Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Radim Kolar Assignee: Mark Miller Priority: Minor Labels: patch Fix For: 4.1, 5.0 Attachments: solr-mergeratelimit.txt, solr-ratelimit2.txt add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505790#comment-13505790 ] Radim Kolar commented on SOLR-4030: --- it still merges into trunk cleanly. just do git pull Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Radim Kolar Assignee: Mark Miller Priority: Minor Labels: patch Fix For: 4.1, 5.0 Attachments: solr-mergeratelimit.txt add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505840#comment-13505840 ] Mark Miller commented on SOLR-4030: --- bq. it still merges into trunk cleanly. Sure, it applies - it does not compile. bq. just do git pull I'm using your patch and an svn checkout - no git to be found. Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Radim Kolar Assignee: Mark Miller Priority: Minor Labels: patch Fix For: 4.1, 5.0 Attachments: solr-mergeratelimit.txt add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505855#comment-13505855 ] Radim Kolar commented on SOLR-4030: --- but it failed to build with 5.x in jenkins. i will take a more detailed look on it Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Radim Kolar Assignee: Mark Miller Priority: Minor Labels: patch Fix For: 4.1, 5.0 Attachments: solr-mergeratelimit.txt add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505866#comment-13505866 ] Radim Kolar commented on SOLR-4030: --- LUCENE-4537 is cause. I will rework it but its not clear if new rate limiter is used for ordinary writes (not just merges) as well. Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Radim Kolar Assignee: Mark Miller Priority: Minor Labels: patch Fix For: 4.1, 5.0 Attachments: solr-mergeratelimit.txt add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505892#comment-13505892 ] Radim Kolar commented on SOLR-4030: --- added limits for reading, merging and writing. Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Radim Kolar Assignee: Mark Miller Priority: Minor Labels: patch Fix For: 4.1, 5.0 Attachments: solr-mergeratelimit.txt, solr-ratelimit2.txt add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505908#comment-13505908 ] Mark Miller commented on SOLR-4030: --- Looks good. I'll look at adding a unit test. I'd also rather detect when no settings have been entered (all unlimited) and not wrap the dir with a rate limiting wrapper in that case. We also do an instance of check in 4x against fsdir - so we should make that work with this. Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Radim Kolar Assignee: Mark Miller Priority: Minor Labels: patch Fix For: 4.1, 5.0 Attachments: solr-mergeratelimit.txt, solr-ratelimit2.txt add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4030) Use Lucene segment merge throttling
[ https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505161#comment-13505161 ] Mark Miller commented on SOLR-4030: --- This would be nice to add - could you update this patch to 5x trunk Radmin? Use Lucene segment merge throttling --- Key: SOLR-4030 URL: https://issues.apache.org/jira/browse/SOLR-4030 Project: Solr Issue Type: Improvement Reporter: Radim Kolar Assignee: Mark Miller Priority: Minor Labels: patch Fix For: 4.1, 5.0 Attachments: solr-mergeratelimit.txt add argument maxMergeWriteMBPerSec to Solr directory factories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
