|
| 1 | +These are paraphrased notes from a live discussion with several people. |
| 2 | +Parenthesis are used where the paraphrasing is particularly distant from what |
| 3 | +the speaker said. Feel free to edit these notes as you see fit. |
| 4 | + |
| 5 | +# 2020-06-26, paper discussion |
| 6 | + |
| 7 | +* lindsey: goal of the summer reading group is to read papers relevant to CASL, |
| 8 | + consistency aware solvers and languages |
| 9 | + * the name has connotations of security, trustworthiness, and beauty |
| 10 | + * the letters can be re-purposed easily (coordination avoiding.. etc) so the |
| 11 | + acronym is reusable |
| 12 | + * we are interested broadly in programming language level ways of (ensuring |
| 13 | + safety guarantees) |
| 14 | + * we decided to read this paper first about strong eventual consistency: |
| 15 | + [Verifying Strong Eventual Consistency in Distributed |
| 16 | + Systems](https://dl.acm.org/doi/10.1145/3133933) by Gomes et al. (OOPSLA |
| 17 | + '17) |
| 18 | + * the CRDT people introduced the term Strong Eventual Consistency (SEC) |
| 19 | + * This paper formally verifies SEC for some CRDTs |
| 20 | + * This paper is special because it treats the network as a first-class |
| 21 | + citizen |
| 22 | + * One problem with much pl research is that the network is (shrugged off or |
| 23 | + assumed out of the proofs) |
| 24 | + * This paper explicitly models the network, and makes assumptions |
| 25 | + explicit, and bakes those things into the verification |
| 26 | + * You could argue with those choices about what assumptions, but at |
| 27 | + least they're there! |
| 28 | +* lindsey: we thought we'd do this paper reading group for 10 weeks |
| 29 | + * it should be student driven, so we can take more than one meeting/week to |
| 30 | + discuss an interesting paper |
| 31 | + * we have a github org https://github.com/lsd-ucsc/CASL |
| 32 | + * here is the reading tentative schedule |
| 33 | + https://github.com/lsd-ucsc/CASL/blob/master/reading-group-schedule.md |
| 34 | + * (lindsey went over the schedule, typist couldn't keep up) |
| 35 | +* lindsey: sometimes having a discussion is easier in smaller groups |
| 36 | + * thinking ahead to teaching in the fall, having breakout rooms might make |
| 37 | + discussion easier |
| 38 | + * we could do 30 minute discussions in smaller groups and then reconvene in |
| 39 | + the bigger group? |
| 40 | + * here are some questions to guide discussion |
| 41 | + 1. What's the paper about? |
| 42 | + 2. What's one thing I learned? |
| 43 | + 3. What's one question I'm curious about? |
| 44 | + 4. What's one step I can take towards answering the question? |
| 45 | +* kamala: this isn't my area and i haven't read the whole paper |
| 46 | + * lindsey: that's ok! i hope we're all (paraphrased: here to discuss it!) |
| 47 | +* lindsey: (creating breakout rooms) |
| 48 | + * [assigning 9 participants into 3 rooms] |
| 49 | + |
| 50 | +[breakout room group] |
| 51 | + |
| 52 | +* we came up with a few questions, then lindsey joined |
| 53 | + * farhad: "is causal consistency stronger or weaker than strong eventual |
| 54 | + consistency?" |
| 55 | + * sohum: "the paper notes that it is sufficient to require that concurrent |
| 56 | + operations commute, even in the presence of operations that can fail. why |
| 57 | + is that sufficient?" (end of section 4.3) |
| 58 | + * lindsey was also curious about that section noted at end of 4.3 |
| 59 | +* lindsey: this paper has a diagram that describes the proof, and also |
| 60 | + describes the paper flow (something to aspire to) |
| 61 | + |
| 62 | +[back to main discussion group] |
| 63 | + |
| 64 | +* lindsey: this is test run for group discussions in the fall classes; thinking |
| 65 | + about roles in the breakout (eg. recorder and speaker for a group) |
| 66 | + * lindsey: this group is more relaxed, but can somebody from each |
| 67 | + breakout group volunteer? |
| 68 | +* kamala: |
| 69 | + * kamala: first we talked about .. (typist couldn't keep up) |
| 70 | + * kamala: then we talked about convergence, and what that means .. (typist |
| 71 | + couldn't keep up) |
| 72 | + * kamala: for me, knowing how the high-level properties are defined as |
| 73 | + "correct" will help to match with the proofs and understand them |
| 74 | + * gan: (with a question related to kamala's question about high level |
| 75 | + definiions) is eventualy consistency the same as "no consistency"? |
| 76 | + * lindsey: i think eventual consistency doesn't belong in the same |
| 77 | + hierarchy as the other consistency models; it's a liveness property |
| 78 | + * lindsey: this paper discusses two safety properties (consistency and |
| 79 | + progress), but there's nothing in here about liveness |
| 80 | + * lindsey: i think kamala raises a good point, which is that normally |
| 81 | + the whole reason we do this is to have better avalability. that's the |
| 82 | + only reason to sacrifice anything other than (linearizability) |
| 83 | + * lindsey: (typist couldn't keep up) .. given that those bad things |
| 84 | + (about the network) that could happen, and this replication algorithm |
| 85 | + or data structure, what kinds of guarantees do we still have? ..it |
| 86 | + depends.. |
| 87 | + * gan: my take (on eventual consistency) is that it says "eventually |
| 88 | + things will converge" but that "eventually" is unbounded |
| 89 | + * gan: but in the paper, they provide a definition (typist couldn't |
| 90 | + keep up) which discusses the sets of messages recieved |
| 91 | + * (patrick, kamala commented; typist couldn't keep up) |
| 92 | + * lindsey: (typist couldn't keep up) this paper doesn't talk about the |
| 93 | + availability guarantees |
| 94 | +* patrick,farhad: "is causal consistency stronger or weaker than strong |
| 95 | + eventual consistency?" |
| 96 | + * lindsey: this paper makes an assumption that causal consistency is baked |
| 97 | + in and isn't discussed |
| 98 | + * lindsey: next week we're going to discuss a paper that shows that causal |
| 99 | + consistency is too strong for some CRDTs and too weak for other CRDTs |
| 100 | + * farhad: it's possible that (inaudible) .. |
| 101 | + * lindsey: right, it could be that the particular definition of strong |
| 102 | + eventual consistency isn't comparable with common definitions of causal |
| 103 | + consistency |
| 104 | + * farhad: my followup question was, what are the differences in the |
| 105 | + guarantees of causal consistency and strong eventual consistency? |
| 106 | + |
| 107 | +* lindsey: ok, we are out of time |
| 108 | + * we haven't discussed this whole paper; we have a choice; we can discuss |
| 109 | + this paper more next time? |
| 110 | + * farhad, kamala, others: let's discuss this paper more next week! |
| 111 | + |
| 112 | +* gan: for the CASL group we should agree on a set of common definitions for |
| 113 | + these concepts! |
| 114 | + * lindsey,others: yes, that's a good idea |
0 commit comments