Reminder: Reminder: Monday is our contributor Sync meeting at 9AM PST/12 AM Eastern/6 PM Central Europe, Here is the Microsoft Teams Link to join the meeting.

set up a reminder on “Monday is our contributor Sync meeting at 9AM PST/12 AM Eastern/6 PM Central Europe, Here is the Microsoft Teams Link to join the meeting.” in this channel at 9AM every other Friday (next occurrence is November 21st), Pacific Standard Time.

was held up joining

Reminder: Monday is our contributor Sync meeting at 9AM PST/12 AM Eastern/6 PM Central Europe, Here is the Microsoft Teams Link to join the meeting.

I must’ve messed up the schedule. Ignore ^

set up a reminder “Monday is our contributor Sync meeting at 9AM PST/12 AM Eastern/6 PM Central Europe, Here is the Microsoft Teams Link to join the meeting.” in this channel at 9AM every other Friday (next occurrence is November 28th), Pacific Standard Time.

I think the docs might need some re-organization… For some reason, towards the beginning, I thought it would be a good idea to split the content into dev/operator/user… then came a few more sections (proposals which maybe ought to have gone under dev, and Quickstart which maybe ought to have gone under user). I see that some of the latest pages were added under quickstart but probably don’t make sense to have over there either. The whole thing probably needs a fresh look. The dev/ops/user separation might not be the right starting point.

Reminder: Monday is our contributor Sync meeting at 9AM PST/12 AM Eastern/6 PM Central Europe, Here is the Microsoft Teams Link to join the meeting.

Good security conference here in MTL. I always thought it’d be interesting to submit a talk about how Venice is used to power various cybersec and privacy things at LI, like scrape detection, MRF, etc… I never got around to it, but maybe you will 😅 ! LMK if you’re in town, I’ll show you around 😉 https://nsec.io/cfp/

Reminder: Monday is our contributor Sync meeting at 9AM PST/12 AM Eastern/6 PM Central Europe, Here is the Microsoft Teams Link to join the meeting.

I've been thinking about isolation levels... technically, it should be possible to implement Snapshot Isolation in Venice while still having A/A (i.e., multi-leader) replication. SI is not a walk in the park to implement if you have a partitioned system, but it is feasible... the A/A DCR could be viewed as the equivalent of write skew / phantom anomalies. Those are only solvable with Serializable Isolation, which is fundamentally incompatible with multi-leader.

That does not mean it would be a good idea to spend effort building SI (or even weaker isolation levels) in Venice... but it's interesting to consider that it's at least possible.

Reminder: Monday is our contributor Sync meeting at 9AM PST/12 AM Eastern/6 PM Central Europe, Here is the Microsoft Teams Link to join the meeting.

Reminder: Monday is our community syncup meeting at 9AM PST/12 PM Eastern/6 PM Central Europe. Here is the Microsoft Teams Link to join the meeting.

Reminder: Monday is our community syncup meeting at 9AM PST/12 PM Eastern/6 PM Central Europe. Here is the Microsoft Teams Link to join the meeting.

Does anybody still have access to the powerpoint slides for my J on the Beach 2025 talk? I think I shared it with a few folks before. Would you mind sharing it either as a file or web link?

Reminder: Monday is our community syncup meeting at 9AM PST/12 PM Eastern/6 PM Central Europe. Here is the Microsoft Teams Link to join the meeting.

Reminder: Monday is our community syncup meeting at 9AM PST/12 PM Eastern/6 PM Central Europe. Here is the Microsoft Teams Link to join the meeting.

Reminder: Monday is our community syncup meeting at 9AM PST/12 PM Eastern/6 PM Central Europe. Here is the Microsoft Teams Link to join the meeting.

Proteus open source -> https://github.com/linkedin/Hoptimator (called hoptimator in OS, this has the Venice connector)

Reminder: Monday is our community syncup meeting at 9AM PST/12 PM Eastern/6 PM Central Europe. Here is the Microsoft Teams Link to join the meeting.

Just heard the news of the layoffs at LI. For those who were still there, I hope it turned out the way you hoped… whether that means keeping your job or getting the package! Thinking of you all. Godspeed.

Reminder: Monday is our community syncup meeting at 9AM PST/12 PM Eastern/6 PM Central Europe. Here is the Microsoft Teams Link to join the meeting.

@Sergey Makagonov 0.4.833 is prod verified

Hi @Koorous Vargha, Hope you had a great long weekend! I have a few questions about Venice, hope you could take a look some time. 1. Safe deployment Curious if you guys have any recommendations for safe deployment of Venice? We had our ingestion jobs failing when servers were being rolled out:

03:48:28 ERROR VenicePushJob:        Kill check monitor detected that push job for store: ..., version: 19 has been killed. Status: ERROR

OfflinePushMonitor

flips an in-flight push to terminal

ERROR

when it briefly sees a replica go

OFFLINE

. To mitigate this, I added retries of the

VenicePushJob

inside of our Whatnot-specific Spark Job, and it helped. I was also looking at

node_removable

API on the controller side and considered adding it into

preStop

hook of servers, - but it looks like it's mostly for decommissioning servers and making sure that the stores remain healthy (it can return

WILL_LOSE_DATA

,

WILL_TRIGGER_LOAD_REBALANCE

). 2. Partition skew mitigation We used replication factor of 3 on our load-test setup with 10 venice servers. There were cases when some servers could have all 3 partitions of present for a particular store - not all active, but still, results in 33% of all reads for such store to be served from this particular server. 3. Per-store RCU quota and per-router quota Looks like the RCU quota is a combination of per-store and per-router quota (hav a write-up on this). I'm curious, what is the

max.read.capacity

config that you use in production for routers? And what are the practical maximum per-store RCUs limits do you set?

🧵 Venice Writes for non-JVM languages Hi team, Sooner or later, we'll need to support writes into Venice outside of VPJ / Flink. We're a Python shop, and while Venice routers provide decent performance for non-JVM languages through HTTP endpoints, supporting ad-hoc writes outside of VPJ/FLink is not trivial, yet it's an obvious ask for Venice which covers the functionality of KV stores. We've evaluated the following options: 1. Python-native Producer - too complex (KME envelope serialization, the DIV state machine (segment numbers, sequence numbers, SOS control messages), partitioner byte-compatibility, schema fetching). Risks of divergence from Java implementation 2. New component -

venice-writer-router

, alongside

venice-router

,

venice-controller

, etc- that will be a Netty HTTP server on top of the

venice-producer

client • pros: ◦ not that hard to implement - we can reuse a bunch of code from router ◦ doesn't have to handle complex use-cases like

write compute

right away - we can start with simple PUT/DELETE for the entire key(s) 3. proxy solution, shipped as a DaemonSet • can be extended further to support fast client and Da-Vinci client for reads. It's very likely we'll explore faster clients down the road. Questions to the community: • I heard from @Ankit that for their C++ service, they used go-proxy (overseeing the Java Da-vinci and Producer), and the writes and reads went through this proxy. Curious if there is any chance this part could be open-sourced? It should be generic enough, doesn't even have to compile, we can pick it up and make it work. Even design docs/proposal would be helpful. • how common is the RT-only pattern for Venice, where writes happen outside of streaming/batch path? cc @Koorous Vargha and @Zac Policzer would appreciate your input and recommendations on the direction.

Reminder: Monday is our community syncup meeting at 9AM PST/12 PM Eastern/6 PM Central Europe. Here is the Microsoft Teams Link to join the meeting.

Reminder: Monday is our community syncup meeting at 9AM PST/12 PM Eastern/6 PM Central Europe. Here is the Microsoft Teams Link to join the meeting.

Reminder: Monday is our community syncup meeting at 9AM PST/12 PM Eastern/6 PM Central Europe. Here is the Microsoft Teams Link to join the meeting.

Reminder: Monday is our community syncup meeting at 9AM PST/12 PM Eastern/6 PM Central Europe. Here is the Microsoft Teams Link to join the meeting.