Re: 4.4 release planning
Steve: So is the plan to address the Permgen issues before releasing and fix it both on the branch and 4x and trunk? On Tue, Jul 9, 2013 at 1:51 AM, Steve Rowe sar...@gmail.com wrote: 4.4 branch created. On Jul 8, 2013, at 12:37 PM, Steve Rowe sar...@gmail.com wrote: As I mentioned a week ago, I plan on branching for 4.4 today, likely late in the day (UTC+4). If all goes well, I'll cut an RC in one week, on July 15th. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: 4.4 release planning
On Tue, Jul 9, 2013 at 7:07 AM, Erick Erickson erickerick...@gmail.com wrote: So is the plan to address the Permgen issues before releasing and fix it both on the branch and 4x and trunk? IMO, it depends if people think it's a test-only issue or not, a hadoop-only issue or not, etc. All bug fixes should also go to the branch unless the risk is too high. -Yonik http://lucidworks.com - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
RE: 4.4 release planning
Hi, Mark created https://issues.apache.org/jira/browse/SOLR-5022 I think at this time it is hard to find out if it’s a serious production issue or just a test issue. The problem is currently that its hard to reproduce consistently and when it reproduces, the JVM is completely dead, not responding to anything (no kill, no debugger attachment, no jmap,...). The issue appears more often with tests.modifier=3, but this is not really telling you it’s a test relict. There are no bad classloaders involved (I checked the dump, all looks fine, do duplicate classes,...), so it looks like something is creating interned strings all the time, which does not play well with our test infrastructure that runs everything in the same JVM, so interned strings never get cleaned up. A fix would be to create a module for running those tests in good-old one JVM per test suite. Until we know *what and *where* the issue is, I see this as blocker. Uwe - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de -Original Message- From: ysee...@gmail.com [mailto:ysee...@gmail.com] On Behalf Of Yonik Seeley Sent: Tuesday, July 09, 2013 2:43 PM To: Lucene/Solr Dev Subject: Re: 4.4 release planning On Tue, Jul 9, 2013 at 7:07 AM, Erick Erickson erickerick...@gmail.com wrote: So is the plan to address the Permgen issues before releasing and fix it both on the branch and 4x and trunk? IMO, it depends if people think it's a test-only issue or not, a hadoop-only issue or not, etc. All bug fixes should also go to the branch unless the risk is too high. -Yonik http://lucidworks.com - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: 4.4 release planning
On Jul 9, 2013, at 8:52 AM, Uwe Schindler u...@thetaphi.de wrote: Until we know *what and *where* the issue is, I see this as blocker. That code has been running for months in the real world on huge amounts of data for long periods of time with no perm gen issues. It's an issue with the resources required by tests and running the dfs mini cluster and creating so many collections. It's not a blocker. - Mark - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: 4.4 release planning
+1 -- Jack Krupansky -Original Message- From: Steve Rowe Sent: Monday, July 08, 2013 12:37 PM To: dev@lucene.apache.org Subject: 4.4 release planning As I mentioned a week ago, I plan on branching for 4.4 today, likely late in the day (UTC+4). If all goes well, I'll cut an RC in one week, on July 15th. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: 4.4 release planning
On 7/8/2013 10:37 AM, Steve Rowe wrote: As I mentioned a week ago, I plan on branching for 4.4 today, likely late in the day (UTC+4). If all goes well, I'll cut an RC in one week, on July 15th. +1 Let's make sure Solr isn't in a vulnerable position like it was when 4.3.0 was released. That will naturally be more on the heads of us Solr devs than the release manager. Thanks, Shawn - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
RE: 4.4 release planning
On 7/8/2013 10:37 AM, Steve Rowe wrote: As I mentioned a week ago, I plan on branching for 4.4 today, likely late in the day (UTC+4). If all goes well, I'll cut an RC in one week, on July 15th. +1 Let's make sure Solr isn't in a vulnerable position like it was when 4.3.0 was released. That will naturally be more on the heads of us Solr devs than the release manager. Can we fix the permgen problems? To me, this is un-releaseable at current stage, the tests hang not only on Jenkins, but locally, too. To me appears all vulnerable :( Robert and me were contacted by Oracle today, if we found new bugs with Java 8 because it is now feature-complete and ready to go next stages - and I would really like to send them a link to the Jenkins server, but it's all red - I would be ashamed showing that to them! To me this looks also not good for users. Uwe - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: 4.4 release planning
4.4 branch created. On Jul 8, 2013, at 12:37 PM, Steve Rowe sar...@gmail.com wrote: As I mentioned a week ago, I plan on branching for 4.4 today, likely late in the day (UTC+4). If all goes well, I'll cut an RC in one week, on July 15th. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
