Been down for 90 minutes now while this delete continues to run. I never know whether to wait it out or kill -9 the server process and deal with data corruption (usually have to restore from backup). Will wait it out a bit longer and see what happens.
On Wednesday, August 26, 2015 at 4:32:36 PM UTC-6, David Carr wrote: > > Doing data cleanup on orientdb 2.1.0... > > I issued console command "delete vertex #21:121048" and for the next 60 > minutes any other (binary in our case) client connections receive this > message: > > *ERROR socket_read(): unable to read from socket [10060]: A connection > attempt failed because the connected party did not properly respond after a > period of time, or established connection failed because connected host has > failed to respond.* > > > When the delete completed all clients could connect normally again. > Orientdb server log files contain (repeatedly): > > *java.net.SocketException: Broken pipe* > > *Error during WAL background flush * > > *java.lang.OutOfMemoryError: Java heap space* > > > This is a real problem to take down an entire db host just to do data > cleanup on one vertex. I'm not sure how many edges it had but presumably > there must have been a lot to cause this big of a problem. Will make > scheduling periodic maintenance a real burden for IT and hardship for end > users. > > Anybody else out there seeing this type of system behavior? > -- --- 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.
