mz_storage/render.rs
1// Copyright Materialize, Inc. and contributors. All rights reserved.
2//
3// Use of this software is governed by the Business Source License
4// included in the LICENSE file.
5//
6// As of the Change Date specified in that file, in accordance with
7// the Business Source License, use of this software will be governed
8// by the Apache License, Version 2.0.
9
10//! Renders ingestions and exports into timely dataflow
11//!
12//! ## Ingestions
13//!
14//! ### Overall structure
15//!
16//! Before describing any of the timely operators involved in ingesting a source it helps to
17//! understand the high level structure of the timely scopes involved. The reason for this
18//! structure is the fact that we ingest external sources with a source-specific, and source
19//! implementation defined, timestamp type which tracks progress in a way that the source
20//! implementation understands. Each source specific timestamp must be compatible with timely's
21//! `timely::progress::Timestamp` trait and so it's suitable to represent timely streams and by
22//! extension differential collections.
23//!
24//! On the other hand, Materialize expects a specific timestamp type for all its collections
25//! (currently `mz_repr::Timestamp`) so at some point the dataflow's timestamp must change. More
26//! generally, the ingestion dataflow starts with some timestamp type `FromTime` and ends with
27//! another timestamp type `IntoTime`.
28//!
29//! Here we run into a problem though because we want to start with a timely stream of type
30//! `Stream<G1: Scope<Timestamp=FromTime>, ..>` and end up using it in a scope `G2` whose timestamp
31//! type is `IntoTime`. Timely dataflows are organized in scopes where each scope has an associated
32//! timestamp type that must refine the timestamp type of its parent scope. What "refines" means is
33//! defined by the [`timely::progress::timestamp::Refines`] trait in timely. `FromTime` however
34//! does not refine `IntoTime` nor does `IntoTime` refine `FromTime`.
35//!
36//! In order to acomplish this we split ingestion dataflows in two scopes, both of which are
37//! children of the root timely scope. The first scope is timestamped with `FromTime` and the
38//! second one with `IntoTime`. To move timely streams from the one scope to the other we must do
39//! so manually. Each stream that needs to be transferred between scopes is first captured using
40//! [`timely::dataflow::operators::capture::capture::Capture`] into a tokio unbounded mpsc channel.
41//! The data in the channel record in full detail the worker-local view of the original stream and
42//! whoever controls the receiver can read in the events, in the standard way of consuming the
43//! async channel, and work with it. How the receiver is turned back into a timely stream in the
44//! destination scope is described in the next section.
45//!
46//! For now keep in mind the general structure of the dataflow:
47//!
48//!
49//! ```text
50//! +----------------RootScope(Timestamp=())------------------+
51//! | |
52//! | +---FromTime Scope---+ +---IntoTime Scope--+ | |
53//! | | | | | |
54//! | | *--+---------+--> | |
55//! | | | | | |
56//! | | <--+---------+--* | |
57//! | +--------------------+ ^ +-------------------+ |
58//! | | |
59//! | | |
60//! | data exchanged between |
61//! | scopes with capture/reclock |
62//! +---------------------------------------------------------+
63//! ```
64//!
65//! ### Detailed dataflow
66//!
67//! We are now ready to describe the detailed structure of the ingestion dataflow. The dataflow
68//! begins with the `source reader` dataflow fragment which is rendered in a `FromTime` timely
69//! scope. This scope's timestamp is controlled by the [`crate::source::types::SourceRender::Time`]
70//! associated type and can be anything the source implementation desires.
71//!
72//! Each source is free to render any arbitrary dataflow fragment in that scope as long as it
73//! produces the collections expected by the rest of the framework. The rendering is handled by the
74//! `[crate::source::types::SourceRender::render] method.
75//!
76//! When rendering a source dataflow we expect three outputs. First, a health output, which is how
77//! the source communicates status updates about its health. Second, a data output, which is the
78//! main output of a source and contains the data that will eventually be recorded in the persist
79//! shard. Finally, an optional upper frontier output, which tracks the overall upstream upper
80//! frontier. When a source doesn't provide a dedicated progress output the framework derives one
81//! by observing the progress of the data output. This output (derived or not) is what drives
82//! reclocking. When a source provides a dedicated upper output, it can manage it independently of
83//! the data output frontier. For example, it's possible that a source implementation queries the
84//! upstream system to learn what are the latest offsets for and set the upper output based on
85//! that, even before having started the actual ingestion, which would be presented as data and
86//! progress trickling in via the data output.
87//!
88//! ```text
89//! resume upper
90//! ,--------------------.
91//! / |
92//! health ,----+---. |
93//! output | source | |
94//! ,-----------| reader | |
95//! / +--,---.-+ |
96//! / / \ |
97//! +-----/----+ data / \ upper |
98//! | health | output/ \ output |
99//! | operator | | \ |
100//! +----------+ | | |
101//! FromTime | | |
102//! scope | | |
103//! -------------------------------------|-----------|---------------|---
104//! IntoTime | | |
105//! scope | ,----+-----. |
106//! | | remap | |
107//! | | operator | |
108//! | +---,------+ |
109//! | / |
110//! | / bindings |
111//! | / |
112//! ,-+-----+--. |
113//! | reclock | |
114//! | operator | |
115//! +-,--,---.-+ |
116//! ,----------´.-´ \ |
117//! _.-´ .-´ \ |
118//! _.-´ .-´ \ |
119//! .-´ ,´ \ |
120//! / / \ |
121//! ,----------. ,----------. ,----------. |
122//! | decode | | decode | .... | decode | |
123//! | output 0 | | output 1 | | output N | |
124//! +-----+----+ +-----+----+ +-----+----+ |
125//! | | | |
126//! | | | |
127//! ,-----+----. ,-----+----. ,-----+----. |
128//! | envelope | | envelope | .... | envelope | |
129//! | output 0 | | output 1 | | output N | |
130//! +----------+ +-----+----+ +-----+----+ |
131//! | | | |
132//! | | | |
133//! ,-----+----. ,-----+----. ,-----+----. |
134//! | persist | | persist | .... | persist | |
135//! | sink 0 | | sink 1 | | sink N | |
136//! +-----+----+ +-----+----+ +-----+----+ |
137//! \ \ / |
138//! `-. `, / |
139//! `-._ `-. / |
140//! `-._ `-. / |
141//! `---------. `-. / |
142//! +`---`---+---, |
143//! | resume | |
144//! | calculator | |
145//! +------+-----+ |
146//! \ |
147//! `-------------------´
148//! ```
149//!
150//! #### Reclocking
151//!
152//! Whenever a dataflow edge crosses the scope boundaries it must first be converted into a
153//! captured stream via the `[mz_timely_util::capture::UnboundedTokioCapture`] utility. This
154//! disassociates the stream and its progress information from the original timely scope and allows
155//! it to be read from a different place. The downside of this mechanism is that it's invisible to
156//! timely's progress tracking, but that seems like a necessary evil if we want to do reclocking.
157//!
158//! The two main ways these tokio-fied streams are turned back into normal timely streams in the
159//! destination scope are by the `reclock operator` and the `remap operator` which process the
160//! `data output` and `upper output` of the source reader respectively.
161//!
162//! The `remap operator` reads the `upper output`, which is composed only of frontiers, mints new
163//! bindings, and writes them into the remap shard. The final durable timestamp bindings are
164//! emitted as its output for consumption by the `reclock operator`.
165//!
166//! The `reclock operator` reads the `data output`, which contains both data and progress
167//! statements, and uses the bindings it receives from the `remap operator` to reclock each piece
168//! of data and each frontier statement into the target scope's timestamp and emit the reclocked
169//! stream in its output.
170//!
171//! #### Partitioning
172//!
173//! At this point we have a timely stream with correctly timestamped data in the mz time domain
174//! (`mz_repr::Timestamp`) which contains multiplexed messages for each of the potential subsources
175//! of this source. Each message selects the output it belongs to by setting the output field in
176//! [`crate::source::types::SourceMessage`]. By convention, the main source output is always output
177//! zero and subsources get the outputs from one onwards.
178//!
179//! However, regardless of whether the output is the main source or a subsource it is treated
180//! identically by the pipeline. Each output is demultiplexed into its own timely stream using
181//! [`timely::dataflow::operators::core::partition::Partition`] and the rest of the ingestion pipeline is
182//! rendered independently.
183//!
184//! #### Resumption frontier
185//!
186//! At the end of each per-output dataflow fragment is an instance of `persist_sink`, which is
187//! responsible for writing the final `Row` data into the corresponding output shard. The durable
188//! upper of each of the output shards is then recombined in a way that calculates the minimum
189//! upper frontier between them. This is what we refer to as the "resumption frontier" or "resume
190//! upper" and at this stage it is expressed in terms of `IntoTime` timestamps. As a final step,
191//! this resumption frontier is converted back into a `FromTime` timestamped frontier using
192//! `ReclockFollower::source_upper_at_frontier` and connected back to the source reader operator.
193//! This frontier is what drives the `OffsetCommiter` which informs the upstream system to release
194//! resources until the specified offsets.
195//!
196//! ## Exports
197//!
198//! Not yet documented
199
200use std::collections::BTreeMap;
201use std::rc::Rc;
202use std::sync::Arc;
203
204use mz_ore::error::ErrorExt;
205use mz_repr::{GlobalId, Row};
206use mz_storage_types::controller::CollectionMetadata;
207use mz_storage_types::dyncfgs;
208use mz_storage_types::oneshot_sources::{OneshotIngestionDescription, OneshotIngestionRequest};
209use mz_storage_types::sinks::StorageSinkDesc;
210use mz_storage_types::sources::{GenericSourceConnection, IngestionDescription, SourceConnection};
211use mz_timely_util::antichain::AntichainExt;
212use mz_timely_util::scope_label::ScopeExt;
213use timely::PartialOrder;
214use timely::dataflow::operators::vec::Map;
215use timely::dataflow::operators::{Concatenate, ConnectLoop, Feedback, Leave};
216use timely::progress::Antichain;
217use timely::worker::Worker as TimelyWorker;
218use tokio::sync::Semaphore;
219
220use crate::healthcheck::{HealthStatusMessage, HealthStatusUpdate, StatusNamespace};
221use crate::source::RawSourceCreationConfig;
222use crate::storage_state::StorageState;
223
224mod persist_sink;
225pub mod sinks;
226pub mod sources;
227
228/// Assemble the "ingestion" side of a dataflow, i.e. the sources.
229///
230/// This method creates a new dataflow to host the implementations of sources for the `dataflow`
231/// argument, and returns assets for each source that can import the results into a new dataflow.
232pub fn build_ingestion_dataflow(
233 timely_worker: &mut TimelyWorker,
234 storage_state: &mut StorageState,
235 primary_source_id: GlobalId,
236 description: IngestionDescription<CollectionMetadata>,
237 as_of: Antichain<mz_repr::Timestamp>,
238 resume_uppers: BTreeMap<GlobalId, Antichain<mz_repr::Timestamp>>,
239 source_resume_uppers: BTreeMap<GlobalId, Vec<Row>>,
240) {
241 let worker_id = timely_worker.index();
242 let worker_logging = timely_worker.logger_for("timely").map(Into::into);
243 let debug_name = primary_source_id.to_string();
244 let name = format!("Source dataflow: {debug_name}");
245 timely_worker.dataflow_core(&name, worker_logging, Box::new(()), |_, root_scope| {
246 let root_scope = root_scope.with_label();
247
248 // Here we need to create two scopes. One timestamped with `()`, which is the root scope,
249 // and one timestamped with `mz_repr::Timestamp` which is the final scope of the dataflow.
250 // Refer to the module documentation for an explanation of this structure.
251 // The scope.clone() occurs to allow import in the region.
252 root_scope.clone().scoped(&name, |mz_scope| {
253 let debug_name = format!("{debug_name}-sources");
254
255 let mut tokens = vec![];
256
257 // One feedback edge per export, so the source pipeline can observe each
258 // export's committed upper individually. Concatenating them would only expose
259 // their meet.
260 let mut export_upper_handles = BTreeMap::new();
261 let mut export_upper_streams = BTreeMap::new();
262 for export_id in description.source_exports.keys() {
263 let (handle, stream) = mz_scope.feedback(Default::default());
264 export_upper_handles.insert(*export_id, handle);
265 export_upper_streams.insert(*export_id, stream);
266 }
267
268 let connection = description.desc.connection.clone();
269 tracing::info!(
270 id = %primary_source_id,
271 as_of = %as_of.pretty(),
272 resume_uppers = ?resume_uppers,
273 source_resume_uppers = ?source_resume_uppers,
274 "timely-{worker_id} building {} source pipeline", connection.name(),
275 );
276
277 let busy_signal = if dyncfgs::SUSPENDABLE_SOURCES
278 .get(storage_state.storage_configuration.config_set())
279 {
280 Arc::new(Semaphore::new(1))
281 } else {
282 Arc::new(Semaphore::new(Semaphore::MAX_PERMITS))
283 };
284
285 // Only Postgres keeps its remap upper still through a snapshot, so only its ceiling
286 // ends near where the frontier lands when the pin lifts. MySQL and SQL Server tick
287 // through theirs, which would hold the shard upper at the as_of for the whole replay.
288 // TODO: include them once their snapshots run concurrently with CDC.
289 let oltp_source = matches!(connection, GenericSourceConnection::Postgres(_));
290
291 let base_source_config = RawSourceCreationConfig {
292 name: format!("{}-{}", connection.name(), primary_source_id),
293 id: primary_source_id,
294 source_exports: description.source_exports.clone(),
295 timestamp_interval: description.desc.timestamp_interval,
296 worker_id: mz_scope.index(),
297 worker_count: mz_scope.peers(),
298 now_fn: storage_state.now.clone(),
299 metrics: storage_state.metrics.clone(),
300 as_of: as_of.clone(),
301 resume_uppers: resume_uppers.clone(),
302 source_resume_uppers,
303 remap_metadata: description.remap_metadata.clone(),
304 persist_clients: Arc::clone(&storage_state.persist_clients),
305 statistics: storage_state
306 .aggregated_statistics
307 .get_ingestion_stats(&primary_source_id),
308 shared_remap_upper: Rc::clone(
309 &storage_state.source_uppers[&description.remap_collection_id],
310 ),
311 // This might quite a large clone, but its just during rendering
312 config: storage_state.storage_configuration.clone(),
313 remap_collection_id: description.remap_collection_id,
314 busy_signal: Arc::clone(&busy_signal),
315 };
316
317 let (outputs, source_health, remap_upper, source_tokens) = match connection {
318 GenericSourceConnection::Kafka(c) => crate::render::sources::render_source(
319 mz_scope,
320 root_scope,
321 &debug_name,
322 c,
323 description.clone(),
324 export_upper_streams,
325 storage_state,
326 base_source_config,
327 ),
328 GenericSourceConnection::Postgres(c) => crate::render::sources::render_source(
329 mz_scope,
330 root_scope,
331 &debug_name,
332 c,
333 description.clone(),
334 export_upper_streams,
335 storage_state,
336 base_source_config,
337 ),
338 GenericSourceConnection::MySql(c) => crate::render::sources::render_source(
339 mz_scope,
340 root_scope,
341 &debug_name,
342 c,
343 description.clone(),
344 export_upper_streams,
345 storage_state,
346 base_source_config,
347 ),
348 GenericSourceConnection::SqlServer(c) => crate::render::sources::render_source(
349 mz_scope,
350 root_scope,
351 &debug_name,
352 c,
353 description.clone(),
354 export_upper_streams,
355 storage_state,
356 base_source_config,
357 ),
358 GenericSourceConnection::LoadGenerator(c) => crate::render::sources::render_source(
359 mz_scope,
360 root_scope,
361 &debug_name,
362 c,
363 description.clone(),
364 export_upper_streams,
365 storage_state,
366 base_source_config,
367 ),
368 };
369 tokens.extend(source_tokens);
370
371 let mut health_streams = Vec::with_capacity(source_health.len() + outputs.len());
372 health_streams.extend(source_health);
373 for (export_id, (ok, err)) in outputs {
374 let export = &description.source_exports[&export_id];
375 let source_data = ok.map(Ok).concat(err.map(Err));
376
377 let metrics = storage_state.metrics.get_source_persist_sink_metrics(
378 export_id,
379 primary_source_id,
380 worker_id,
381 &export.storage_metadata.data_shard,
382 );
383
384 tracing::info!(
385 id = %primary_source_id,
386 "timely-{worker_id}: persisting export {} of {}",
387 export_id,
388 primary_source_id
389 );
390
391 // An export snapshots when its resume upper is at or below the as_of. The
392 // controller uses the same test to hand the connector a minimum from-time resume
393 // upper.
394 let snapshotting = oltp_source
395 && resume_uppers
396 .get(&export_id)
397 .is_some_and(|upper| PartialOrder::less_equal(upper, &as_of));
398 let (upper_stream, errors, sink_tokens) = crate::render::persist_sink::render(
399 mz_scope,
400 export_id,
401 export.storage_metadata.clone(),
402 source_data,
403 storage_state,
404 metrics,
405 Arc::clone(&busy_signal),
406 snapshotting.then(|| as_of.clone()),
407 description.desc.timestamp_interval,
408 remap_upper.clone(),
409 );
410 let feedback_handle = export_upper_handles
411 .remove(&export_id)
412 .expect("each output corresponds to a source export");
413 upper_stream.connect_loop(feedback_handle);
414 tokens.extend(sink_tokens);
415
416 let sink_health = errors.map(move |err: Rc<anyhow::Error>| {
417 let halt_status =
418 HealthStatusUpdate::halting(err.display_with_causes().to_string(), None);
419 HealthStatusMessage {
420 id: None,
421 namespace: StatusNamespace::Internal,
422 update: halt_status,
423 }
424 });
425 health_streams.push(sink_health.leave(root_scope));
426 }
427
428 // Assert explicitly for debugging. Timely only builds a feedback operator in
429 // `connect_loop`, so a handle left here would fail dataflow construction with an
430 // opague error.
431 assert!(
432 export_upper_handles.is_empty(),
433 "source rendered no output for exports {:?}",
434 export_upper_handles.keys(),
435 );
436
437 let health_stream = root_scope.concatenate(health_streams);
438 let health_token = crate::healthcheck::health_operator(
439 root_scope,
440 storage_state.now.clone(),
441 resume_uppers
442 .iter()
443 .filter_map(|(id, frontier)| {
444 // If the collection isn't closed, then we will remark it as Starting as
445 // the dataflow comes up.
446 (!frontier.is_empty()).then_some(*id)
447 })
448 .collect(),
449 primary_source_id,
450 "source",
451 health_stream,
452 crate::healthcheck::DefaultWriter {
453 command_tx: storage_state.internal_cmd_tx.clone(),
454 updates: Rc::clone(&storage_state.shared_status_updates),
455 },
456 storage_state
457 .storage_configuration
458 .parameters
459 .record_namespaced_errors,
460 dyncfgs::STORAGE_SUSPEND_AND_RESTART_DELAY
461 .get(storage_state.storage_configuration.config_set()),
462 );
463 tokens.push(health_token);
464
465 storage_state
466 .source_tokens
467 .insert(primary_source_id, tokens);
468 })
469 });
470}
471
472/// do the export dataflow thing
473pub fn build_export_dataflow(
474 timely_worker: &mut TimelyWorker,
475 storage_state: &mut StorageState,
476 id: GlobalId,
477 description: StorageSinkDesc<CollectionMetadata, mz_repr::Timestamp>,
478) {
479 let worker_logging = timely_worker.logger_for("timely").map(Into::into);
480 let debug_name = id.to_string();
481 let name = format!("Source dataflow: {debug_name}");
482 timely_worker.dataflow_core(&name, worker_logging, Box::new(()), |_, scope| {
483 let scope = scope.with_label();
484
485 let mut tokens = vec![];
486 let (health_stream, sink_tokens) =
487 crate::render::sinks::render_sink(scope, storage_state, id, &description);
488 tokens.extend(sink_tokens);
489
490 // Note that sinks also have only 1 active worker, which simplifies the work that
491 // `health_operator` has to do internally.
492 let health_token = crate::healthcheck::health_operator(
493 scope,
494 storage_state.now.clone(),
495 [id].into_iter().collect(),
496 id,
497 "sink",
498 health_stream,
499 crate::healthcheck::DefaultWriter {
500 command_tx: storage_state.internal_cmd_tx.clone(),
501 updates: Rc::clone(&storage_state.shared_status_updates),
502 },
503 storage_state
504 .storage_configuration
505 .parameters
506 .record_namespaced_errors,
507 dyncfgs::STORAGE_SUSPEND_AND_RESTART_DELAY
508 .get(storage_state.storage_configuration.config_set()),
509 );
510 tokens.push(health_token);
511
512 storage_state.sink_tokens.insert(id, tokens);
513 });
514}
515
516pub(crate) fn build_oneshot_ingestion_dataflow(
517 timely_worker: &mut TimelyWorker,
518 storage_state: &mut StorageState,
519 ingestion_id: uuid::Uuid,
520 collection_id: GlobalId,
521 collection_meta: CollectionMetadata,
522 description: OneshotIngestionRequest,
523) {
524 let (results_tx, results_rx) = tokio::sync::mpsc::unbounded_channel();
525 let callback = move |result| {
526 // TODO(cf3): Do we care if the receiver has gone away?
527 //
528 // Persist is working on cleaning up leaked blobs, we could also use `OneshotReceiverExt`
529 // here, but that might run into the infamous async-Drop problem.
530 let _ = results_tx.send(result);
531 };
532 let connection_context = storage_state
533 .storage_configuration
534 .connection_context
535 .clone();
536 let enforce_external_addresses = mz_storage_types::dyncfgs::ENFORCE_EXTERNAL_ADDRESSES
537 .get(storage_state.storage_configuration.config_set());
538
539 let name = format!("Oneshot ingestion: {ingestion_id}");
540 let tokens = timely_worker.dataflow_named(&name, |scope| {
541 let scope = scope.with_label();
542 mz_storage_operators::oneshot_source::render(
543 scope,
544 Arc::clone(&storage_state.persist_clients),
545 connection_context,
546 collection_id,
547 collection_meta,
548 description,
549 enforce_external_addresses,
550 callback,
551 )
552 });
553 let ingestion_description = OneshotIngestionDescription {
554 tokens,
555 results: results_rx,
556 };
557
558 storage_state
559 .oneshot_ingestions
560 .insert(ingestion_id, ingestion_description);
561}