Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tool/logs: flushable ingests not parsed #2899

Closed
sumeerbhola opened this issue Sep 14, 2023 · 0 comments · Fixed by #2906
Closed

tool/logs: flushable ingests not parsed #2899

sumeerbhola opened this issue Sep 14, 2023 · 0 comments · Fixed by #2906

Comments

@sumeerbhola
Copy link
Collaborator

So these don't appear in the stats.

We are able to parse normal ingests that look like:

I230831 04:35:56.104308 4914199 3@pebble/event.go:709 ⋮ [n10,s10,pebble] 32038  [JOB 6633] ingested L5:034936 (1.3KB), L0:034941 (1.0KB), L0:034937 (1.9KB), L0:034938 (1.1KB), L0:034939 (1.0KB), L0:034940 (1.0KB)

But flushable ingests appear as:

I230831 04:35:55.077939 4911865 3@pebble/event.go:685 ⋮ [n10,s10,pebble] 31971  [JOB 6623] flushed 6 ingested flushables L5:034895 (1.3KB) + L0:034900 (1.0KB) + L0:034896 (2.1KB) + L0:034897 (1.1KB) + L0:034898 (1.0KB) + L4:034899 (1.0KB) in 0.0s (0.0s total), output rate 4.4MB/s
@bananabrick bananabrick self-assigned this Sep 15, 2023
bananabrick added a commit that referenced this issue Sep 20, 2023
There are two kinds of log lines which are relevant to flushable
ingestions.

The first one is of the form:
```
ingested as flushable 024323 (1.5KB), 024328 (1.0KB), 024324 (2.0KB), 024325 (1.1KB), 024326 (1.1KB), 024327 (54KB)
```

The second one is of the form:
```
flushed 6 ingested flushables L0:024323 (1.5KB) + L0:024328 (1.0KB) + L0:024324 (2.0KB) + L2:024325 (1.1KB) + L2:024326 (1.1KB) + L0:024327 (54KB) in 0.0s (0.0s total), output rate 152MB/s
```

The first type gets printed when we perform a flushable ingestion, and
the second type gets printed when we actually ingest the sstables during
the flush.

For now, we ignore the first log type, and parse the second log type
as ingestions.

On the following logs:
```
I230831 04:13:28.689575 3717 3@pebble/event.go:685 ⋮ [n10,s10,pebble] 345  [JOB 219] flushed 6 ingested flushables L0:024323 (1.5KB) + L0:024328 (1.0KB) + L0:024324 (2.0KB) + L2:024325 (1.1KB) + L2:024326 (1.1KB) + L0:024327 (54KB) in 0.0s (0.0s total), output rate 152MB/s

I230831 04:13:28.824280 3780 3@pebble/event.go:685 ⋮ [n10,s10,pebble] 365  [JOB 226] flushed 6 ingested flushables L0:024334 (1.5KB) + L0:024339 (1.0KB) + L0:024335 (1.9KB) + L0:024336 (1.1KB) + L0:024337 (1.1KB) + L0:024338 (12KB) in 0.0s (0.0s total), output rate 67MB/s
```

We get the following ingestion summary:
```
_kind______from______to_____________________________________count___bytes______time
flush                L0                                         2   227KB        0s
ingest               L0                                        10    77KB
ingest               L2                                         2   2.2KB
total                                                          14   306KB        0s
_kind______from______to___default____move___elide__delete___count___in(B)__out(B)__mov(B)__del(B)______time
compact      L2      L3         2       0       0       0       2    31MB    31MB      0B      0B        0s
compact      L3      L4         0       4       0       0       4      0B      0B    60MB      0B        0s
compact      L4      L5         2       3       0       0       5    64MB    64MB    32MB      0B        0s
compact      L5      L6         4       0       0       0       4   320MB   320MB      0B      0B        0s
compact      L6      L6         0       0      32       1      33   1.3GB   1.3GB      0B   4.4MB        3s
total                           8       7      32       1      48   1.7GB   1.7GB    92MB   4.4MB        4s
```

Fixes: #2899
@jbowens jbowens moved this to Done in [Deprecated] Storage Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants