Hi Ram,
Thank you very much for the detailed information.
The only strange thing I see in the logs is the following
--> com.orientechnologies.orient.core.exception.OCommandExecutionException:
Class 'NULL' was not found in current database [ONetworkProtocolHttpDb]
2019-08-21 12:03:39:675 SEVERE
To add more details the problem,
We have more than 500+ queries/API built on 200+ vertex based schema. All
the query were written optimally with right indexes so that at any normal
condition the response time of the queries will be under 50 ms. Most of the
query response in less than 20 ms. You
Hi Ram
It's hard to give you a quick solution with so few information.
V 2.0 is EOL so we will hardly release a community patch, but we can try to
troubleshoot the problem and see if we can work around it.
Can you provide a bit more information, eg. server logs, typical workload,
some information
We are using OrientDB ver 2.0.18, and we are facing a critical issue for
the past 5 days. The following issues we are facing
1. Orient DB server is unreachable frequently
2. We cannot able to shut down the server. We are forced to kill the DB
3. Sometimes the Index gets crashed.
The
