Re: Unexpectly short DHT entry lifetime
marty1885 <[email protected]> Mon, 15 May 2023 04:07:43 +0000
| Newsgroups | gmane.network.gnunet.general |
|---|---|
| Message-ID | <W1vh7DXkwRmw33zPLJKC8u4eplG_EMLBaSSMxwT6zCIJOFuvbWGY8LEPQyES08vfiT8-y7K-vebmIR3xQJrHdCGC2RxsfmPK-c4ZhCdXSa4=@protonmail.com> |
Hi Martin, I increased the cache and routing table size and that seems to do the trick. Didn't try restarting GNUnet on it's own. Not sure what fixed it. Best ------- Original Message ------- On Tuesday, May 9th, 2023 at 11:38 PM, Schanzenbach, Martin <[email protected]> wrote: > Hi Martin, > > I just tested this and I don't get results at all. Not even when I am > not connected to the network. > This may be related to some recent changes to the DHT. > > BR > > Am 09.05.23 um 08:02 schrieb marty1885: > > > Hi all, > > > > I've been messing around with GNUnet and building fun applications with it. One thing I noticed recently. Looking at the source code of gnunet-dht-put. The default lifetime of a DHT entry should be an hour1. But when I run the following command. The key `hello` is not found via the get command just 5 minutes or less later. > > > > > gnunet-dht-put -k "hello" -d "world" # Set hello to world > > > # Running immediately after set works > > > gnunet-dht-get -k "hello" -T 10000000 > > > Result 0, type 8: > > > world > > > sleep 300 > > > gnunet-dht-get -k "hello" -T 10000000 > > > # No key found > > > > Am I doing something wrong? My application needs the DHT to bootstrap group information. > > > > Best, > > Martin