Multiple deployment of letta sever pointing to same db results in duplicate persona and human entries

[raolak]

Describe the bug
I have requirement where I need more than one letta service (server per workflow). But when I install the server, seems like duplicate data's being ingested for Human and persona blocks. May be its part of boostraping server. We can make all the name fields of entities with unique constraint, so that we will not allow any duplicate entities creation with same name.

Refer attached screenshot

Please describe your setup

• How did you install letta?
  • I install letta using helm per workflow..but it points to same db instance
• Describe your setup
  • Letta is deployed on k8s...
  • using docker which runs letta startup scripts

Screenshots
Attached

[sarahwooders]

Why do you need multiple letta servers? The service is designed to support multiple agents. There are probably conflicts between the servers since they are connecting to the same DB.

[raolak]

Hi Sarah, The discussion is outlined here: GitHub Issue Comment <#2021 (comment)>. A single server could suffice if the tools didn’t rely on local resources. However, in my case, I embedded Letta alongside my service because the tools need to operate on local resources. For example, tasks like cloning, Docker build and deploy, and other similar use cases require local processes. Additionally, scenarios like analytics may not necessitate executing tools on the Letta server itself, as they depend on interacting with local resources and processes. Hope my understanding is clear ! And may be there is a better way to do this . Best regards, _lnr

…

On Thu, 21 Nov 2024 at 10:24 AM, Sarah Wooders ***@***.***> wrote: Why do you need multiple letta servers? The service is designed to support multiple agents. There are probably conflicts between the servers since they are connecting to the same DB. — Reply to this email directly, view it on GitHub <#2079 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGPZOPKMQY7C55XBGJDSPT2BVRRDAVCNFSM6AAAAABSGCE5W6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJQGA3TONBQGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>