Hi Rafał Kuć I got it,the point is many operating systems measure time in units of tens of milliseconds,and the System.currentTimeMillis() is just base on operating system. In my case,I just do DIH with a crontable, Is there any possiblity to get in that trouble?I am really can not picture what the situation may lead to the problem.
Thanks very much. 2014-04-26 20:49 GMT+08:00 YouPeng Yang <yypvsxf19870...@gmail.com>: > Hi Mark Miller > Sorry to get you in these discussion . > I notice that Mark Miller report this issure in > https://issues.apache.org/jira/browse/SOLR-5734 according to > https://issues.apache.org/jira/browse/SOLR-5721,but it just happened with > the zookeeper. > If I just do DIH with JDBCDataSource ,I do not think it will get the > problem. > Please give some hints > > >> Bonus,just post the last mail I send about the problem: > > I have just compare the difference between the version 4.6.0 and 4.7.1. > Notice that the time in the getConnection function is declared with the > System.nanoTime in 4.7.1 ,while System.currentTimeMillis(). > Curious about the resson for the change.the benefit of it .Is it > neccessory? > I have read the SOLR-5734 , > https://issues.apache.org/jira/browse/SOLR-5734 > Do some google about the difference of currentTimeMillis and nano,but > still can not figure out it. > > Thank you very much. > > > 2014-04-26 20:31 GMT+08:00 YouPeng Yang <yypvsxf19870...@gmail.com>: > > Hi >> I have just compare the difference between the version 4.6.0 and >> 4.7.1. Notice that the time in the getConnection function is declared >> with the System.nanoTime in 4.7.1 ,while System.currentTimeMillis(). >> Curious about the resson for the change.the benefit of it .Is it >> neccessory? >> I have read the SOLR-5734 , >> https://issues.apache.org/jira/browse/SOLR-5734 >> Do some google about the difference of currentTimeMillis and nano,but >> still can not figure out it. >> >> >> >> >> 2014-04-26 2:24 GMT+08:00 Shawn Heisey <s...@elyograg.org>: >> >> On 4/25/2014 11:56 AM, Hutchins, Jonathan wrote: >>> >>>> I recently upgraded from 4.6.1 to 4.7.1 and have found that the DIH >>>> process that we are using takes 4x as long to complete. The only odd >>>> thing I notice is when I enable debug logging for the dataimporthandler >>>> process, it appears that in the new version each sql query is resulting >>>> in >>>> a new connection opened through jdbcdatasource (log: >>>> http://pastebin.com/JKh4gpmu). Were there any changes that would >>>> affect >>>> the speed of running a full import? >>>> >>> >>> This is most likely the problem you are experiencing: >>> >>> https://issues.apache.org/jira/browse/SOLR-5954 >>> >>> The fix will be in the new 4.8 version. The release process for 4.8 is >>> underway right now. A second release candidate was required yesterday. If >>> no further problems are encountered, the release should be made around the >>> middle of next week. If problems are encountered, the release will be >>> delayed. >>> >>> Here's something very important that has been mentioned before: Solr >>> 4.8 will require Java 7. Previously, Java 6 was required. Java 7u55 (the >>> current release from Oracle as I write this) is recommended as a minimum. >>> >>> If a 4.7.3 version is built, this is a fix that we should backport. >>> >>> Thanks, >>> Shawn >>> >>> >> >
