[Bamboo-Users] The block of broken node

Binary binary at eniak.org
Sat Dec 29 04:09:39 UTC 2007


Oh, i was omit the tag of <initargs>, my fault.
In fact, the config files of GATEWAY and NODE is:

[mabin at proxy1 mabin]$ cat /etc/gateway.cfg 
# $Id: gateway.cfg,v 1.6 2006/03/21 15:28:44 srhea Exp $
<sandstorm>
    <global>
        <initargs>
            node_id 192.168.209.37:3630
        </initargs>
    </global>

    <stages>
        <Network>
            class bamboo.network.Network
            <initargs>
            </initargs>         
        </Network>
        
        <Router>
            class bamboo.router.Router
            <initargs>
                gateway_count 1
                gateway_0     192.168.209.37:3630
                leaf_set_size 1
                digit_values 16
                location_cache_size 64
                immediate_join true
            </initargs>
        </Router>

        <Rpc>
            class bamboo.lss.Rpc
            <initargs>
            </initargs>
        </Rpc>

        <DataManager>
            class bamboo.dmgr.DataManager
            <initargs>
                debug_level           0
                merkle_tree_expansion 2
                desired_replicas      64
            </initargs>
        </DataManager>

        <StorageManager>
            class bamboo.db.StorageManager
            <initargs>
                homedir       /home/mabin/tmp/node
                libdb_cache_size 67108864
            </initargs>
        </StorageManager>

        <Dht>
            class bamboo.dht.Dht
            <initargs>
                debug_level 0
                storage_manager_stage StorageManager
                min_replica_count     1
            </initargs>
        </Dht>  

        <Gateway>                                                             
            class bamboo.dht.Gateway
            <initargs>
                debug_level 0
                port 3639
            </initargs>
        </Gateway>                          

        <WebInterface>
            class bamboo.www.WebInterface
            <initargs>
                storage_manager_stage StorageManager
            </initargs>
        </WebInterface>

       <Vivaldi>
           class bamboo.vivaldi.Vivaldi
           <initargs>
               vc_type          2.5d
               generate_pings   true
               eavesdrop_pings  false
               use_reverse_ping true
               ping_period      10000
               version          1
           </initargs>
       </Vivaldi>

    </stages>
</sandstorm>
[mabin at proxy1 mabin]$ 

[mabin at proxy1 mabin]$ cat /etc/node.cfg
# $Id: node.cfg,v 1.6 2006/03/21 15:28:44 srhea Exp $
<sandstorm>
    <global>
        <initargs>
            node_id 192.168.209.33:3630
        </initargs>
    </global>

    <stages>
        <Network>
            class bamboo.network.Network
            <initargs>
            </initargs>         
        </Network>
        
        <Router>
            class bamboo.router.Router
            <initargs>
                gateway_count 1
                gateway_0     192.168.209.37:3630
                leaf_set_size 1
                digit_values 16
                location_cache_size 64
                immediate_join true
            </initargs>
        </Router>

        <Rpc>
            class bamboo.lss.Rpc
            <initargs>
            </initargs>
        </Rpc>

        <DataManager>
            class bamboo.dmgr.DataManager
            <initargs>
                debug_level           0
                merkle_tree_expansion 2
                desired_replicas      64
            </initargs>
        </DataManager>

        <StorageManager>
            class bamboo.db.StorageManager
            <initargs>
                homedir       /home/mabin/tmp/node
                libdb_cache_size 67108864
            </initargs>
        </StorageManager>

        <Dht>
            class bamboo.dht.Dht
            <initargs>
                debug_level 0
                storage_manager_stage StorageManager
                min_replica_count     1
            </initargs>
        </Dht>  

        <Gateway>                                                             
            class bamboo.dht.Gateway
            <initargs>
                debug_level 0
                port 3639
            </initargs>
        </Gateway>                          

        <WebInterface>
            class bamboo.www.WebInterface
            <initargs>
                storage_manager_stage StorageManager
            </initargs>
        </WebInterface>

       <Vivaldi>
           class bamboo.vivaldi.Vivaldi
           <initargs>
               vc_type          2.5d
               generate_pings   true
               eavesdrop_pings  false
               use_reverse_ping true
               ping_period      10000
               version          1
           </initargs>
       </Vivaldi>

    </stages>
</sandstorm>
[mabin at proxy1 mabin]$ 

step 1: Running GATEWAY
		run-java -mx128M bamboo.lss.DustDevil /etc/gateway.cfg

step 2: Running NODE, join the GATEWAY
		run-java -mx128M bamboo.lss.DustDevil /etc/node.cfg

step 3: Client put/get something, the action like this:
		while( 1 )
		{
			const char* url = "http://192.168.209.37:3631"; // the URL of GATEWAY
			dht_put( url, key, val, 3600 * 24 * 7 );
			dht_get( url, key, val, sizeof( val ) );
		}

step 4: Terminate the NODE (192.168.209.33).

step 5: The client blocked, until NODE removed by GATEWAY.

Thanks very much.

------------------				 
Binary
2007-12-29

-------------------------------------------------------------
发件人:Mosiuoa Tsietsi
发送日期:2007-12-29 04:00:22
收件人:Binary
抄送:jacasey at deakin.edu.au; bamboo-users
主题:Re: [Bamboo-Users] The block of broken node

Hi Binary,

I was unable to reproduce the problem you are having. When an overlay is
running and one node terminates abruptly, the overlay does not block.
The config file you posted also wouldn't run because you did not specify
the node_id in the <initargs> tag (but that doesn't seem to be the
problem you are having, unless the config you posted and the actual
config you are using are different). Try the generic config files on the
website such as  http://bamboo-dht.org/first.cfg and see if you don't
have better luck.

Cheers,

Mos

On Sat, 2007-12-29 at 01:08 +0800, Binary wrote:
> Dear all:
> I have encountered a problem on bamboo block.
> 
> If any node is invalid in the bamboo network operation, the whole network will be blocked until the invalid node removed. Usually, it takes me over 100 seconds, which is really a long duration for my work, to wait for the problem removal.
> 
> How can I solve the node problem within 3 seconds?
> Thank you very much and your reply will be appreciated.
> 
> BTW, could you please provide me with a man page or the introduction about the configure?
> 
> Binary 
> 
> 
> _______________________________________________
> Bamboo-Users mailing list
> Bamboo-Users at bamboo-dht.org
> http://bamboo-dht.org/cgi-bin/mailman/listinfo/bamboo-users
> 
-- 
The Law of Unintended Consequences:  for every action, there is an
excellent chance of producing an opposite and totally disproportionate
reaction. - Clyde Haberman



More information about the Bamboo-Users mailing list