Analytics Vasiliki (Vasia) Kalavri
 vkalavri@bu.edu Spring 2020 3/31: High-availability & reconfiguration ??? Vasiliki Kalavri | Boston University 2020 • To recover from failures, the system needs fails it immediately. 7 Restart strategies ??? Vasiliki Kalavri | Boston University 2020 Reconfiguration with Savepoints ??? Vasiliki Kalavri | Boston University 2020 • Change parallelism • scale • skew and straggler mitigation • Migrate to a different cluster or software version 9 Reconfiguration cases ??? Vasiliki Kalavri | Boston University 2020 Streaming applications are long-running

Apache Flink wordcount Every reconfiguration takes ~30s during which the system is unavailable 28 DS2 scaling actions on Apache Flink wordcount Every reconfiguration takes ~30s during which the incoming records block channels and upstream operators All affected operators block until the reconfiguration is complete • State is scoped to a single task • Each stateful task is responsible for

section. Reconfiguration of a “local” MSP is only possible manually, and requires that the peer or orderer process is restarted. In subsequent releases we aim to offer online/dynamic reconfiguration (i.e. MSP in the mspconfig folder, and setting that path in the relevant section in configtx.yaml. Reconfiguration of an MSP on the channel, including announcements of the certificate revocation lists associated an intermediate CA. As mentioned in previous sections, reconfiguration of an MSP is achieved by reconfiguration mechanisms (manual reconfiguration for the local MSP instances, and via properly constructed

master Reconfiguration of a “local” MSP is only possible manually, and requires that the peer or orderer process is restarted. In subsequent releases we aim to offer online/dynamic reconfiguration (i.e. MSP in the mspconfig folder, and setting that path in the relevant section in configtx. yaml. Reconfiguration of an MSP on the channel, including announcements of the certificate revocation lists associated an intermediate CA. As mentioned in previous sections, reconfiguration of an MSP is achieved by reconfiguration mechanisms (manual reconfiguration for the local MSP instances, and via properly constructed

section. Reconfiguration of a “local” MSP is only possible manually, and requires that the peer or orderer process is restarted. In subsequent releases we aim to offer online/dynamic reconfiguration (i.e. MSP in the mspconfig folder, and setting that path in the relevant section in configtx. yaml. Reconfiguration of an MSP on the channel, including announcements of the certificate revocation lists associated an intermediate CA. As mentioned in previous sections, reconfiguration of an MSP is achieved by reconfiguration mechanisms (manual reconfiguration for the local MSP instances, and via properly constructed

section. Reconfiguration of a “local” MSP is only possible manually, and requires that the peer or orderer process is restarted. In subsequent releases we aim to offer online/dynamic reconfiguration (i.e. MSP in the mspconfig folder, and setting that path in the relevant section in configtx.yaml. Reconfiguration of an MSP on the channel, including announcements of the certificate revocation lists associated an intermediate CA. As mentioned in previous sections, reconfiguration of an MSP is achieved by reconfiguration mechanisms (manual reconfiguration for the local MSP instances, and via properly constructed

section. Reconfiguration of a “local” MSP is only possible manually, and requires that the peer or orderer process is restarted. In subsequent releases we aim to offer online/dynamic reconfiguration (i.e. MSP in the mspconfig folder, and setting that path in the relevant section in configtx.yaml. Reconfiguration of an MSP on the channel, including announcements of the certificate revocation lists associated an intermediate CA. As mentioned in previous sections, reconfiguration of an MSP is achieved by reconfiguration mechanisms (manual reconfiguration for the local MSP instances, and via properly constructed

section. Reconfiguration of a “local” MSP is only possible manually, and requires that the peer or orderer process is restarted. In subsequent releases we aim to offer online/dynamic reconfiguration (i.e. MSP in the mspconfig folder, and setting that path in the relevant section in configtx. yaml. Reconfiguration of an MSP on the channel, including announcements of the certificate revocation lists associated an intermediate CA. As mentioned in previous sections, reconfiguration of an MSP is achieved by reconfiguration mechanisms (manual reconfiguration for the local MSP instances, and via properly constructed

section. Reconfiguration of a “local” MSP is only possible manually, and requires that the peer or orderer process is restarted. In subsequent releases we aim to offer online/dynamic reconfiguration (i.e. MSP in the mspconfig folder, and setting that path in the relevant section in configtx.yaml. Reconfiguration of an MSP on the channel, including announcements of the certificate revocation lists associated an intermediate CA. As mentioned in previous sections, reconfiguration of an MSP is achieved by reconfiguration mechanisms (manual reconfiguration for the local MSP instances, and via properly constructed

section. Reconfiguration of a “local” MSP is only possible manually, and requires that the peer or orderer process is restarted. In subsequent releases we aim to offer online/dynamic reconfiguration (i.e. MSP in the mspconfig folder, and setting that path in the relevant section in configtx. yaml. Reconfiguration of an MSP on the channel, including announcements of the certificate revocation lists associated Documentation, Release master As mentioned in previous sections, reconfiguration of an MSP is achieved by reconfiguration mechanisms (manual reconfiguration for the local MSP instances, and via properly constructed