Hi,
You should set as much as you have RAM in such way that part of the memory
will not be in swap.
On Wed, Oct 8, 2014 at 10:37 PM, odbuser wrote:
> I wasn't setting this:
> storage.diskCache.bufferSize
>
> But what value should be used? I can't figure it out from your message or
> documenta
Hi everyone,
I am really excited about using the lucene indexes with OrientDB. I have a
few questions for the experts ;)
I have not successfully created indexes on embedded objects/maps. Is it
possible?
Customer : {
address {
city:
country: ...
}
}
How can
Running the Document API "Introduction" code, I get this message in my
console output:
Oct 08, 2014 9:30:20 PM com.orientechnologies.common.log.OLogManager log
WARNING: Your maximum heap size is 2.17GB, but OrientDB uses off-heap
memory to avoid GC pauses. In the case OrientDB is running as stan
I wasn't setting this:
storage.diskCache.bufferSize
But what value should be used? I can't figure it out from your message or
documentation.
I use 256MB or 512MB heap. This particular database is smaller than
Stefan's and I'm seeing the same issues but not as soon. I would prefer if
the data
That works, thanks.
On Tuesday, October 7, 2014 12:52:07 PM UTC-6, Keith Freeman wrote:
>
> See this console output:
>
> orientdb {server=remote:localhost/}> connect remote:localhost/petshop root
> root
>
> Disconnecting from remote server [remote:localhost/]...
> OK
> Connecting to database [rem
Hi Cosmin,
you mentioned it before but i didn't noticed it, yes the local database
has been deprecated since a while, and has been completely removed in
the 2.0* version.
use everytime the plocal that will work :)
Kind Regards,
Emanuel
On 10/08/2014 12:28 PM, Cosmin Cătălin Sanda wrote:
> Hi E
You should add user and password after 'drop' command, The same like with
creating database
orientdb {db=petshop}> drop database remote:localhost/petshop root root
should work.
W dniu wtorek, 7 października 2014 20:52:07 UTC+2 użytkownik Keith Freeman
napisał:
>
> See this console output:
>
Hi Emanuel,
I always made sure I use the same client and server version. Having a
*local* database doesn't seem to allow successfully inserting ODocuments.
Changing the database type to *plocal* did the trick. I consider this
matter solved as if I understand correctly, *plocal* is going to be t
Hi Cosmin,
Which version of the server are you using ? is it also 1.7.8?
An issue of this kind can happen if the server and the client don't have
exactly the same protocol.
we guarantee the backward compatibility, and it may be there an issue,
know both version of the server and client can help u
Any help here is much appreciated
--
---
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 orient-database+unsubscr...@googlegroups.com.
For more options, visit https:/
Enabling debugging of the binary protocol revealed the following:
tldr
2014-10-08 10:22:15:596 INFO /127.0.0.1:50296 - Read byte: 0
[OChannelBinaryServer]
2014-10-08 10:22:15:601 INFO /127.0.0.1:50296 - Writing byte (1 byte): 0
[OChannelBinaryServer]
2014-10-08 10:22:15:601 INFO /127.0.0.1:50296
I am not able to pinpoint the issue exactly, but it seems to be around the
*do *loop in *com.orientechnologies.orient.client.remote.createRecord* and
having something to do with
*com.orientechnologies.orient.core.config.readInt*.
OrientDB <- Asynch Client (/127.0.0.1:2424)@1069 daemon, prio=5,
Thatcher is something ))
Could send me stack trace where infinite loop is going on ?
On Oct 8, 2014 10:16 AM, "Cosmin Cătălin Sanda"
wrote:
> Hi Andrey,
>
> The same behaviour is exposed. Records gets inserted, program doesn't
> finish. The debug shows how it is stuck at the *save* method.
>
> On
Hi Andrey,
The same behaviour is exposed. Records gets inserted, program doesn't
finish. The debug shows how it is stuck at the *save* method.
On Wednesday, October 8, 2014 8:21:14 AM UTC+2, Andrey Lomakin wrote:
>
> Hi,
> Does it work if you provide not server but db user ?
> I mean
>
> ODatab
Hi Jeremie,
the in-memory storage is intended to provide memory only, volatile
behavior, so when you shutdown your machine you will lose all your data.
If you need data persistence you have to use a disk based storage (plocal).
If your concern is about having all your database in memory to have ve
15 matches
Mail list logo
