#3 Failure upon quick successive puts

closed-works-for-me
5
2007-01-03
2006-12-14
Mos
No

Hi,

I am using OpenChord 1.0 for some research that I am doing. I am doing comparison tests with it and Bamboo. Basically, I am threading new Chord nodes in quick succession, where each node creates (or joins) the DHT and subseqently inserts a record into the DHT. After this is done, I run another chord node which joins and then searches for those keys in the DHT. I have run the code successfully where no records are inserted, and I was able to run 50 nodes at a time. I can run and do inserts and fetches with about 5 nodes, but as soon as I create about 10 nodes and above, the code hangs and no insertions are made. Is there a problem with OpenChord such that quick successive puts cause problems in the DHT? Thanks.

Mos

Discussion

  • Mos

    Mos - 2006-12-14
    • priority: 5 --> 9
     
  • Sven Kaffille

    Sven Kaffille - 2007-01-03
    • priority: 9 --> 5
     
  • Sven Kaffille

    Sven Kaffille - 2007-01-03

    Logged In: YES
    user_id=1435049
    Originator: NO

    Hi Mos,

    Can you please provide more information about your setting. E.g. provide the chord.properties file you are using.
    Are you really using Open Chord 1.0. If that is the case, please switch to Open Chord 1.0.1.

    Kind regards

    sven

     
  • Sven Kaffille

    Sven Kaffille - 2007-01-03
    • assigned_to: nobody --> skaffille
     
  • Sven Kaffille

    Sven Kaffille - 2007-01-03
    • status: open --> open-works-for-me
     
  • Sven Kaffille

    Sven Kaffille - 2007-01-03

    Logged In: YES
    user_id=1435049
    Originator: NO

    File Added: Bug1615936.java

     
  • Sven Kaffille

    Sven Kaffille - 2007-01-03
    • status: open-works-for-me --> closed-works-for-me
     
  • Sven Kaffille

    Sven Kaffille - 2007-01-03

    Logged In: YES
    user_id=1435049
    Originator: NO

    I attached a file I used to start a great number of chord peers of Open Chord 1.0.1 under Windows XP Professional.
    It takes three parameters. The local Address (e.g. 192.168.0.1:4242), the bootstrap address (e.g. 192.168.0.4:3232), and a flag that indicates if the peer should leave immediately or be kept alive. To quickly start a number of nodes a batch or shell script can be used.

    Afterwards one can connect to the chord network with help of the console and look for the values the peers inserted before. All peers insert their IP-Address and their port as a key and associate it with the same String as value. (e.g. retrieveN -key 192.168.0.1:4242)

    No peer was blocked while joining the network or inserting a value.

    Kind regards

    sven

     
  • Sven Kaffille

    Sven Kaffille - 2007-01-03

    Logged In: YES
    user_id=1435049
    Originator: NO

    File Added: Bug1615936.java

     
  • Sven Kaffille

    Sven Kaffille - 2007-01-03

    Java File with main method used to reconstruct the behavior described.

     
  • Sven Kaffille

    Sven Kaffille - 2007-01-03

    Logged In: YES
    user_id=1435049
    Originator: NO

    PS:
    Please try to increase the number of Threads used for invocations in the chord.properties file:

    de.uniba.wiai.lspi.chord.com.socket.InvocationThread.corepoolsize=10
    de.uniba.wiai.lspi.chord.com.socket.InvocationThread.maxpoolsize=50

    sven

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks