Re: [Neo] threading

2009-10-13 Thread Johan Svensson
Yes I remember but that bug was triggered by concurrently executing
getSingleRelatoinship and create/delete relationship (and it's fixed
now).

My guess is that if this is a bug (it may very well be but I need some
code that triggers it) the problem will be found in the fairly new
iterable implementation.

-Johan

On Mon, Oct 12, 2009 at 10:01 PM, Mattias Persson
matt...@neotechnology.com wrote:
 Johan I recognize these characteristics from a previous bug (in the
 normal EmbeddedNeo). Do you remember it as well? So if there's an old
 ticket we perhaps could find it and get a clue from there?

 2009/10/11, Johan Svensson jo...@neotechnology.com:
 On Sun, Oct 11, 2009 at 6:01 PM, Marc Preddie mpred...@gmail.com wrote:
...
___
Neo mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user


Re: [Neo] threading

2009-10-12 Thread Mattias Persson
Johan I recognize these characteristics from a previous bug (in the
normal EmbeddedNeo). Do you remember it as well? So if there's an old
ticket we perhaps could find it and get a clue from there?

2009/10/11, Johan Svensson jo...@neotechnology.com:
 On Sun, Oct 11, 2009 at 6:01 PM, Marc Preddie mpred...@gmail.com wrote:
 Hi Johan,
 That's what I initially suspected, and so I ran a small test to output the
 relationship in question, and there is only one.

 But wouldn't the same error occur when using a single thread, if there
 were
 more than one relationship of the same type and I invoked
 getSingleRelationship...

 If there is no writing going on it shouldn't matter if you are reading
 with one or many threads, they should all return the same
 relationships.


 If it helps at all I'm running on winxp 64bit.

 I'm going to try to replicate the issue with using a small sample and if I
 can, would it be helpful to send it you?


 It would be very helpful if you can send me sample code that reproduce
 the issue.

 Regards,
 -Johan
 ___
 Neo mailing list
 User@lists.neo4j.org
 https://lists.neo4j.org/mailman/listinfo/user



-- 
Mattias Persson, [matt...@neotechnology.com]
Neo Technology, www.neotechnology.com
___
Neo mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user


Re: [Neo] threading

2009-10-11 Thread Johan Svensson
Marc,

Could you check if the node that you invoke getSingleRelationship on
actually has one relationship (of BELONGS_TO_CATEGORY, OUTGOING) when
you only perform read operations. You could use the shell (see
http://wiki.neo4j.org/content/Shell) and go to the node listing all
relationships:

// go to node 149816 and list relationships
neo-sh (0)$ cd -a 149816
neo-sh (0)$ ls

-Johan

On Sat, Oct 10, 2009 at 4:35 PM, Marc Preddie mpred...@gmail.com wrote:
 Hi Johan,
 No, I am strictly reading from the graph. I have single read only instance
 which I am attempting to use across multiple threads as you suggest.

 Regards,
 Marc

 On Sat, Oct 10, 2009 at 9:23 AM, Johan Svensson 
 jo...@neotechnology.comwrote:

 Hi,

 Do you have a NeoService writing to the store concurrently with the
 embedded read only ones?

 Regarding the other question you should use one NeoService (instance)
 per machine/across multiple threads. The read only instance is more
 suitable when your graph does not change and you need to load balance
 reads over multiple machines.

 Regards,
 -Johan

 On Thu, Oct 8, 2009 at 11:52 PM, Marc Preddie mpred...@gmail.com wrote:
  Hi,
  When using multiple threads if I use normal (non readonly)  neo and
 lucene
  index everything works perfectly. If I use the readonly versions of neo
 and
  luceneIndex; I begin to get errors of the sort
  ---
   More than one relationship[BELONGS_TO_CATEGORY, OUTGOING] found for
  NodeImpl#149816
  ---
  from ... NodeImpl.getSingleRelationship. If I use the readonly versions
 from
  a single thread everything works.
 
  Has anyone come across this issue? I'm using build 3108.
 
  One other question I have is would it better to use a readonly neo/index
  instance per thread or use a single neo/index across multiple threads?
 
  Regards,
  Marc
___
Neo mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user


Re: [Neo] threading

2009-10-11 Thread Johan Svensson
On Sun, Oct 11, 2009 at 6:01 PM, Marc Preddie mpred...@gmail.com wrote:
 Hi Johan,
 That's what I initially suspected, and so I ran a small test to output the
 relationship in question, and there is only one.

 But wouldn't the same error occur when using a single thread, if there were
 more than one relationship of the same type and I invoked
 getSingleRelationship...

If there is no writing going on it shouldn't matter if you are reading
with one or many threads, they should all return the same
relationships.


 If it helps at all I'm running on winxp 64bit.

 I'm going to try to replicate the issue with using a small sample and if I
 can, would it be helpful to send it you?


It would be very helpful if you can send me sample code that reproduce
the issue.

Regards,
-Johan
___
Neo mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user


Re: [Neo] threading

2009-10-10 Thread Marc Preddie
Hi Johan,
No, I am strictly reading from the graph. I have single read only instance
which I am attempting to use across multiple threads as you suggest.

Regards,
Marc

On Sat, Oct 10, 2009 at 9:23 AM, Johan Svensson jo...@neotechnology.comwrote:

 Hi,

 Do you have a NeoService writing to the store concurrently with the
 embedded read only ones?

 Regarding the other question you should use one NeoService (instance)
 per machine/across multiple threads. The read only instance is more
 suitable when your graph does not change and you need to load balance
 reads over multiple machines.

 Regards,
 -Johan

 On Thu, Oct 8, 2009 at 11:52 PM, Marc Preddie mpred...@gmail.com wrote:
  Hi,
  When using multiple threads if I use normal (non readonly)  neo and
 lucene
  index everything works perfectly. If I use the readonly versions of neo
 and
  luceneIndex; I begin to get errors of the sort
  ---
   More than one relationship[BELONGS_TO_CATEGORY, OUTGOING] found for
  NodeImpl#149816
  ---
  from ... NodeImpl.getSingleRelationship. If I use the readonly versions
 from
  a single thread everything works.
 
  Has anyone come across this issue? I'm using build 3108.
 
  One other question I have is would it better to use a readonly neo/index
  instance per thread or use a single neo/index across multiple threads?
 
  Regards,
  Marc
 ___
 Neo mailing list
 User@lists.neo4j.org
 https://lists.neo4j.org/mailman/listinfo/user

___
Neo mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user