Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [leshan-dev] Shared Redis instance
I've only found information about the graceful restart combined with DTLS, so I guess that's not the solution for me, or did I miss something there? 
Leshan mainly provide Interface for its stores.
It also provide in memory implementation of stores to have something usable out of the box. By the past, we begin to work about providing an out of the box way to use Leshan in a cluster but we finally stop that way to focus on LWM2M core feature. I mean the idea is to provide an API to make it possible to use it in cluster but not to provide an out of the box solution. Anyway, the RedisRegistrationStore is a kind of legacy about this cluster project, we keep it because user seems to use it and this also is another implementation example of the stores but clearly not the core of the project.
About graceful restart, the current implementation does the job as Registration and Observation are persisted in real time, but there is other solution like load-on-start and save-on-stop (The drawback with that solution is you can lost state on crash) Anyway feel free to implement your own store, with your preferred persistence way and your preferred back-end, I mean RedisRegistrationStore is not the only way to persist. 

HTH

Le 24/03/2022 à 11:42, Eva Rott a écrit :

Hi,

thanks for the quick response.

> Let me ask back, why do you want to use redis at all?
> To persist some state? The DTLS session? The lwm2m data (registrations and observe-requests)?
I would indeed like to persist the lwm2m registrations and observations across application / server restarts. 

> (Maybe you looking more for something as a "graceful restart".)
I've only found information about the graceful restart combined with DTLS, so I guess that's not the solution for me, or did I miss something there? 

Best regards
Eva



On 24.03.22 10:18, Kraus Achim (IOB/PAD-DDA-HU) via leshan-dev wrote:

Hi Eva,
I have a question concerning the use of Redis. I have multiple Leshan servers with few clients registered on each and I'd like to use only one Redis instance for all of them. 

Let me ask back, why do you want to use redis at all?
To persist some state? The DTLS session? The lwm2m data (registrations and observe-requests)?
Usually redis was used in order to share that data among several nodes of a cluster.
If there is a different requirement or useful function, I guess you should address that more directly. 
(Maybe you looking more for something as a "graceful restart".)
   Mit freundlichen Grüßen / Best regards

  Achim Kraus

Bosch IoT Hub - Product Area IoT Platform (IOC/PAP-HU)
Bosch.IO GmbH | Postfach 30 02 40 | 70442 Stuttgart | GERMANY | www.bosch.io 
Besucheradresse: Grönerstraße 5/1 | 71636 Ludwigsburg

Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B
Aufsichtsratsvorsitzender: Stefan Koss; Geschäftsführung: Dr. Andreas Nauerz, Yvonne Reckling 


-----Original Message-----
From: leshan-dev <leshan-dev-bounces@xxxxxxxxxxx> On Behalf Of Eva Rott
Sent: Mittwoch, 23. März 2022 21:53
To: leshan-dev@xxxxxxxxxxx
Subject: [leshan-dev] Shared Redis instance

Hi,
I have a question concerning the use of Redis. I have multiple Leshan servers with few clients registered on each and I'd like to use only one Redis instance for all of them.
Now I was wondering, how I could achieve that. For example, is it possible to add a prefix to the Redis keys? E.g. FIRST_APP:REG:EP, OTHER_APP:REG:EP.
The only other thing I've found so far is the database int value that can be specified when creating the JedisPool. This would be my fallback solution but I'd definitely prefer not having to keep track of the database IDs.
I've also thought about overriding/modifying the Redis key prefixes in the RedisRegistrationStore but since they are private I'm not really considering going toward that direction. 


Any help will be very much appreciated.

Thanks in advance.

Best regards
Eva
_______________________________________________
leshan-dev mailing list
leshan-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.eclipse.org%2Fmailman%2Flistinfo%2Fleshan-dev&amp;data=04%7C01%7Cachim.kraus%40bosch.io%7C9f7b9eba1c0147fa5bc908da0d0f278f%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C637836656546740005%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=F0bJ81IgZ1NHWlh24n5nNPaIsFSwxEl5OggkWRIYHvE%3D&amp;reserved=0 
_______________________________________________
leshan-dev mailing list
leshan-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/leshan-dev 
_______________________________________________
leshan-dev mailing list
leshan-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/leshan-dev

Back to the top