[orientdb] OTimeoutException: Can not lock record for 2000 ms Error in 2.0.4

Hi OrientDB team, We are using OrientDB 2.0.4 in CentOS. Our Web application runs Orientdb as an embedded server with plocal connetion. We got some errors like this from our production server yesterday. Here is the stack trace: com.orientechnologies.orient.core.exception.ODatabaseException:

[orientdb] Re: Record deadlock issue in 2.0.2

I am getting this error too. Any progress on this issue? My application is running OrientDB 2.0.4 Jing -- --- 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

[orientdb] LockObtainFailedException when creating Luncen index in 2.0.3

Hi OrientDB team, I am getting this error from the console when I try to create Lucene index. I use plocal connection and here is what I got from the console: orientdb {db=ndex} create index idx_baseterm_name on baseterm (name) FULLTEXT ENGINE LUCENE; Creating index...{db=ndex} Error on

[orientdb] Memory footprint of db export command

Hi OrientDB team, In our production environment (OrientDB 1.7.10), we ran into heap memory issues a couple of times during database export. I am wondering if you have have an estimate of the memory footprint during db export? Does the memory requirement increases when the db grows? Is the

[orientdb] Concurrent Modification in graph API

Hi there, I have a question about a concurrency issue. I have 3 nodes A, B and C in the database. There is a lightweight edge from A to B. There is also an edge from C to B. Now I have 2 threads running concurrently, Thread 1 is deleting node A using OrientVertex.remove() function. Thread 2

[orientdb] Re: Like query and indexs

Hi Erik, The Lucene result looks correct to me. Lucene index tokenizes your original string and creates index. so select location from geo where location lucene kansas* should be the same as select location from geo where location like %kansas% Jing On Thursday, January 22, 2015 at

Re: [orientdb] Re: Cannot unlock a never acquired lock error

Could you also fix it in the 1.7.10 branch? We are seeing this quite often in our production server lately. It makes the record unwritable and we have to keep bouncing our server. Thanks for your. Best, Jing On Friday, January 16, 2015 at 3:35:34 PM UTC-8, Lvc@ wrote: Hi Jing, We fixed

Re: [orientdb] Does Orientdb-lucene Do Any Stemming?

Thanks Riccardo. On Wednesday, January 14, 2015 at 11:52:34 PM UTC-8, Riccardo Tasso wrote: As far as I know (and confirmed by documentation https://github.com/orientechnologies/orientdb-lucene/wiki/Full-Text-Index ) orientdb-lucene uses lucene StandardAnalyzer (

[orientdb] Re: Exclusive lock issue

We also have some locking issues in our application. We couldn't figure out the causes from the error message. It would be nice if the OritentDB team can provide detailed documentation ( in both SQL and Document API level)about the locking strategy, and what are the recommended implementations

[orientdb] Re: Cannot unlock a never acquired lock error

More information on this error. When this error happens, the record will no longer be readable. Thanks, Jing -- --- 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

[orientdb] Cannot unlock a never acquired lock error

Hi, We are getting a ODatabaseException from our application, and I see this Cannot unlock a never acquired lock error message in the stack trace. What does this error mean? How can we avoid it? We are using 1.7.10 under CentOS. com.orientechnologies.orient.core.exception.ODatabaseException:

Re: [orientdb] Re: Lucene Index Error Relate to Database Close command.

-lucene/1.7.10/orientdb-lucene-1.7.10-dist.jar Try it and tell me if the issue still occurs Enrico 2015-01-14 0:14 GMT+01:00 Jing Chen jingj...@gmail.com javascript:: Great! Thanks. On Tuesday, January 13, 2015 at 3:06:57 PM UTC-8, Enrico Risa wrote: Hi Jing tomorrow i will roll a release

[orientdb] Does Orientdb-lucene Do Any Stemming?

Hi OrientDB team, First of all, thanks for your quick response and having a new Orientdb-lucene release out. We are trying out the latest Orientdb-lucene release (oreintdb-lucene-1.7.0-dist.jar) in Orientdb-1.7.10. I had the impression that Orientdb-lucene was doing stemming, but tests show

Re: [orientdb] Re: Lucene Index Error Relate to Database Close command.

Hi Enrico, This error came out again and completely brought the search function down in our production site. It becomes a very critical issue for us, and we really appreciate if you can help us to resolve this issue. Here are some more information I found from our tomcat log. Hope it can

Re: [orientdb] Re: Lucene Index Error Relate to Database Close command.

this problem Enrico 2015-01-13 10:47 GMT+01:00 Jing Chen jingj...@gmail.com javascript:: Hi Enrico, This error came out again and completely brought the search function down in our production site. It becomes a very critical issue for us, and we really appreciate if you can help us

Re: [orientdb] Re: Lucene Index Error Relate to Database Close command.

Great! Thanks. On Tuesday, January 13, 2015 at 3:06:57 PM UTC-8, Enrico Risa wrote: Hi Jing tomorrow i will roll a release with some backports from 2.0, so you can try if resolve this issue. I will send you the link 2015-01-14 0:03 GMT+01:00 Jing Chen jingj...@gmail.com javascript:: Hi

Re: [orientdb] Re: Lucene Index Error Relate to Database Close command.

, January 9, 2015 at 10:17:39 AM UTC-8, Enrico Risa wrote: Hi Jing I see that seems that somehow the index was closed ad then start to give the second error. i'm trying to replicate it any hint on how can replicate it? 2015-01-09 19:09 GMT+01:00 Jing Chen jingj...@gmail.com javascript:: Hi

Re: [orientdb] Memory footprint of Orient-Lucene index

-06 18:17 GMT+01:00 Jing Chen jingj...@gmail.com javascript:: Hi Enrico, I have sent you some memory profile data by email. Please check your gmail. Thanks, Jing -- --- You received this message because you are subscribed to the Google Groups OrientDB group. To unsubscribe from

[orientdb] Re: Lucene Index Error Relate to Database Close command.

Hi Enrico, Could you take a look of this problem? What could be the cause of it and is there anything we can do in our application to avoid this? This error failed all the search functions on our production server. Thanks, Jing On Monday, January 5, 2015 at 11:32:12 AM UTC-8, Jing Chen wrote

Re: [orientdb] Memory footprint of Orient-Lucene index

Hi Enrico, I have sent you some memory profile data by email. Please check your gmail. Thanks, Jing -- --- 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

Re: [orientdb] Memory footprint of Orient-Lucene index

profiling session? 2014-12-30 19:05 GMT+01:00 Jing Chen jingj...@gmail.com javascript:: Thanks for the quick response Enrico. Our application is a tomcat web application running on a Amazon Redhat 7 instance which has 3.5G memory. We have 3G allocated to tomcat JVM. Here are the error

Re: [orientdb] Memory footprint of Orient-Lucene index

Transactions? how many records in insert? 2015-01-05 18:27 GMT+01:00 Jing Chen jingjing...@gmail.com: Hi Enrico, Yes, we are executing massive insert using the Java API directly. What profiling tool do you use? Thanks, Jing On Tuesday, December 30, 2014 10:47:23 AM UTC-8, Enrico Risa wrote

[orientdb] Lucene Index Error Relate to Database Close command.

Hi Enrico and the OrientDB team, We are seeing some Lucene index errors in our application. Our application was trying to close a database connection when it caught an OLockException. Then the graph database shutdown function OrientBaseGraph.shutdown() seems to trigger a Lucene Index error

[orientdb] Lucene TimeoutException during bulk insert

Hi, We have another error which seems to relate to Orient-Lucene. It happened during our massive insert process. The stack trace is attached: [NdexPersistenceService]com.orientechnologies.common.concur.OTimeoutException: Timeout on acquiring exclusive lo ck against resource of class: class

Re: [orientdb] Memory footprint of Orient-Lucene index

) at org.apache.lucene.index.IndexWriter.commitInternal(IndexWriter.java:3022) ... On Tuesday, December 30, 2014 12:52:50 AM UTC-7, Enrico Risa wrote: Hi Jin Chen can you tell me the configuration of your application? Do you have some log or profiling session? 2014-12-30 5:49 GMT+01:00 Jing Chen

[orientdb] Memory footprint of Orient-Lucene index

. Is there a way to estimate the memory footprint of Orientdb-lucene index? When our database grows, does the memory requirement of Lucene index grow as well? Thanks advance for your answers. Jing Chen -- --- You received this message because you are subscribed to the Google Groups OrientDB group

[orientdb] OrientDB ODirectMemoryViolationException

Hi, We got this error from our application. Did anybody see this before? What does this exception mean? Looks like we can't write anything to the db now. We are using 1.7.9 plocal connection pool in our application. The OS is CentOS.

[orientdb] Database error when creating edges using graph API through remote connection

Hi, We are using the 1.7.9-SNAPSHOT version through remote access. In our application, all edges are created by the Graph API funcions. The code that creates the edges are like this: ODocument citationDoc = elementIdCache.get(citationId) ; if (citationDoc ==

[orientdb] java.lang.IllegalMonitorStateException from OrientDB

Hi OrientDB team, We are using 1.7.8 community edition. I saw these message in my program. java.lang.IllegalMonitorStateException at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:155) at

Re: [orientdb] java.lang.IllegalMonitorStateException from OrientDB

Thanks Andrey. Is there a 1.7.9 package that I can download, or do I need to build one from GitHub? -- --- 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

Re: [orientdb] java.lang.IllegalMonitorStateException from OrientDB

by another user (db=v4 your=v3) On Tuesday, September 9, 2014 11:22:41 AM UTC-7, Andrey Lomakin wrote: Hi Jing I fixed similar bug on 1.7.9 could you try it ? On Tue, Sep 9, 2014 at 8:55 PM, Jing Chen jingj...@gmail.com javascript: wrote: Hi OrientDB team, We are using 1.7.8 community

[orientdb] Get available connections in a connection pool

Hi We are using OrientDB 1.7.8. In my code, I created a connection pool using ODatabaseDocumentPool. I was trying to monitor the usage of my connection pool. According to the documentation, it seems that I can use this function ODatabaseDocumentPool

[orientdb] Where can we find 1.7.8 release notes

Hi there, We are currently running on OrientDB 1.7.7 and I would like to find out if we should upgrade our system to 1.7.8. Where can we find the Release notes of 1.7.8? Thanks, Jing -- --- You received this message because you are subscribed to the Google Groups OrientDB group. To

[orientdb] Re: Where can we find 1.7.8 release notes

Thanks Curtis! On Tuesday, August 19, 2014 12:48:53 PM UTC-7, Curtis Mosters wrote: https://groups.google.com/forum/#!topic/orient-database/TehlSTzcpXg It seems that this release has no bug fix list or so. Am Dienstag, 19. August 2014 21:04:19 UTC+2 schrieb Jing Chen: Hi there, We

[orientdb] What does this crc check is failed error mean?

Hi there, I noticed this error in the OrientDB server log today when I was loading data to the database: 2014-08-08 11:09:42:355 SEVE Can not restore 0 WAL master record for storage ndex crc check is failed [OWriteAheadLog] What does this error mean? Should I worry about the data being

[orientdb] Code Migration from 1.6.4 to 1.7.7

Hi everyone, We have an application running on OrientDB version 1.6.4. When I migrate the application to OrientDB 1.7.7, I found that my update functions are not committed to the database any more. I am using the OrientDB Java API, and the process is something like this: // get a connection