Hi guys, If nobody find the problem with 1.7.6 in the next 12 hours I can release it.
Lvc@ On 15 July 2014 00:25, Jebb Stewart <[email protected]> wrote: > I have started running the 1.7.6-SNAPSHOT. I usually don't see the error > until 24-48 hours of uptime. I will update this thread then. Thanks. > > On Monday, July 14, 2014 10:09:20 AM UTC-6, Andrey Lomakin wrote: > >> Hi, >> It is fixed in 1.7.6-SNAPSHOT. >> Could you try it ? >> >> >> On Mon, Jul 14, 2014 at 6:31 PM, Jebb Stewart <[email protected]> >> wrote: >> >>> Looking into this problem a little further. It appears only one of my >>> tables has been corrupted related to this error, when querying against this >>> table I see the following error >>> >>> -1 >>> -> java.util.ArrayList.elementData(ArrayList.java:400) >>> -> java.util.ArrayList.get(ArrayList.java:413) >>> -> com.orientechnologies.orient.core.storage.impl.local. >>> paginated.wal.OWriteAheadLog.flush(OWriteAheadLog.java:733) >>> -> com.orientechnologies.orient.core.index.hashindex.local. >>> cache.OWOWCache.flushPage(OWOWCache.java:1082) >>> -> com.orientechnologies.orient.core.index.hashindex.local. >>> cache.OWOWCache.access$1000(OWOWCache.java:67) >>> -> com.orientechnologies.orient.core.index.hashindex.local. >>> cache.OWOWCache$PeriodicFlushTask.iterateBySubRing(OWOWCache.java:291) >>> -> com.orientechnologies.orient.core.index.hashindex.local. >>> cache.OWOWCache$PeriodicFlushTask.flushRing(OWOWCache.java:254) >>> -> com.orientechnologies.orient.core.index.hashindex.local. >>> cache.OWOWCache$PeriodicFlushTask.run(OWOWCache.java:222) >>> -> java.util.concurrent.Executors$RunnableAdapter. >>> call(Executors.java:471) >>> -> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) >>> -> java.util.concurrent.ScheduledThreadPoolExecutor$ >>> ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) >>> -> java.util.concurrent.ScheduledThreadPoolExecutor$ >>> ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) >>> -> java.util.concurrent.ThreadPoolExecutor.runWorker( >>> ThreadPoolExecutor.java:1145) >>> -> java.util.concurrent.ThreadPoolExecutor$Worker.run( >>> ThreadPoolExecutor.java:615) >>> -> java.lang.Thread.run(Thread.java:744)Exception during data flush. >>> nullException during data flush. >>> null >>> 2014-07-11 14:51:58:746 WARN Page in file observation.pcl with index >>> 1684 was placed in wrong free list, this error will be fixed automatically. >>> [OPaginatedCluster]Exception during data flush. >>> nullException during data flush. >>> null >>> >>> >>> >>> The other tables appear to be functioning normally. >>> >>> Thanks. >>> >>> >>> On Monday, July 14, 2014 8:49:12 AM UTC-6, Jebb Stewart wrote: >>>> >>>> I see these errors in the latest 1.7.5. release as well, although the >>>> database continues to function normally. After this exception, I continue >>>> to see many "nullException during data flush errors". About 1 a second >>>> filling up the log file. >>>> >>>> I am running 1.7.5 with WAL enabled on Linux. >>>> >>>> >>>> -- >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "OrientDB" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Best regards, >> Andrey Lomakin. >> >> Orient Technologies >> the Company behind OrientDB >> >> -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
