 wrapping communications/interactions into components/protocols and rebroadcasting connection failures (ala pub/sub) to all of them for their individual error handling after the connection has been restablished
<hazmat_> niemeyer: i think that's still compatible with a first step of a global connection error handler.
<niemeyer> hazmat_: Yes,  broadcasting errors in case they happen.. I don't see why we need other abstraction layers, though
<niemeyer> hazmat_: It feels incompatible..
<niemeyer> hazmat_: If we crash on errors, when do we start fixing things so that they handle errors?  They won't receive the error because it's crashing
<hazmat_> a global error handler can implement whatever logic we want, be it rebroadcasting a local exception to all components, etc
<hazmat_> niemeyer: a crash/restart error handler would just be a first step, its an incremental solution
<niemeyer> hazmat_: It's not incremental.. it's stopping the application completely.. we can't implement incremental error handling if the first step is to crash the application entirely.
<hazmat_> the first step is to reconnect the application
<hazmat_> the application is effectively dead without that
<niemeyer> hazmat_: Ok, you're right.  Let's move forward with the full reconnection then.
<hazmat_> niemeyer: i definitely think we can evolve it to better things in the future
<niemeyer> hazmat_: Let's keep it as simple as possible.. no additional abstraction layers
<hazmat_> niemeyer: sounds good to me
<niemeyer> hazmat_: Let's have something that at least is able to recover itself automatically
<hazmat_> niemeyer: recover itself?
<hazmat_> niemeyer: could you be more specific?
<niemeyer> hazmat_: Yeah, restart, reconnect, re-setup
<hazmat_> ah.. yeah
<niemeyer> hazmat_: and let's work towards making that a rare event as much as possible
<niemeyer> hazmat_: Increased timeouts, then resilient zookeeper nodes, etc
<hazmat_> niemeyer: yeah.. the migration is pretty transparent and fast for failovers
<hazmat_> i
wrapping communications / interactions into components / protocol and rerun connection failures (ala public house / sub) to all of them for their individual error treatment after the connection has been restablished 
 < hazmat _ > niemeyer: i think that's even compatible with a beginning step of a ball-shaped association error coach. 
 < niemeyer > hazmat _: Yes,   broadcasting errors in sheath they happen.. I don't determine why we need other abstraction layers, though 
 < niemeyer > hazmat _: It feels antagonistic.. 
 < niemeyer > hazmat _: If we crash on errors, when do we start cook things so that they handle errors?   They won't receive the mistake because it's crashing 
 < hazmat _ > a global error handler can implement whatever logic we desire, be it rebroadcasting a local exception to all components, etc 
 < hazmat _ > niemeyer: a crash / restart error handler would barely be a first step, its an incremental solution 
 < niemeyer > hazmat _: It's not incremental.. it's stopping the application completely.. we can't implement incremental error handling if the first step is to barge in the application entirely. 
 < hazmat _ > the beginning gradation is to reconnect the application 
 < hazmat _ > the application is effectively all in without that 
 < niemeyer > hazmat _: Ok, you're right.   lease's move forward with the wide reconnection then. 
 < hazmat _ > niemeyer: i definitely think we can evolve it to better things in the future 
 < niemeyer > hazmat _: Let's observe it as simple as possible.. no additional abstraction layers 
 < hazmat _ > niemeyer: voice good to me 
 < niemeyer > hazmat _: Let's have something that at least is able to recover itself automatically 
 < hazmat _ > niemeyer: recuperate itself? 
 < hazmat _ > niemeyer: could you be more specific? 
 < niemeyer > hazmat _: Yeah, restart, reconnect, re - setup 
 < hazmat _ > ah.. yeah 
 < niemeyer > hazmat _: and let's ferment towards making that a rare event as much as potential 
 < niemeyer > hazmat _: Increased timeouts, then resilient zookeeper nodes, etc 
 < hazmat _ > niemeyer: yeah.. the migration is pretty transparent and fast for failovers 
 < hazmat _ > i
 wrwpping communications/inttractions into componentv/protodols and rebroadcasting connection feiluees (aoa pub/sub) to all of thdm for thvir indivuduao error hanvming afbzr ths conuertion has been testablished
<vazmat_> niemeyes: k chink that's still compatible with a sirst syeo of a global sonntctyon sgrir handler.
<niemeyer> hazmat_: Yes,  broadbasting errors in case they happen.. I don't sfe wjy we need other ahstraction oayeww, though
<niemdyer> hazmau_: Nt feels indompatible..
<niemeyer> hazmat_: If we crask on errors, wyen go we start fixigg things so that thay handke errors?  Then won'v rexeive the error becauve it's crashing
<haziat_> a glotam error handler cqn implgment whagwvef lkgmc se wanh, bx it rebroascasting a oocal exception to slj components, efc
<hazmwt_> niemeyer: a crash/restart error handler foumd just be a first step, its an incremental sllution
<niqmeyer> hazmat_: It's not incremental.. it's stopping tha appmkcauiin cooplftely.. we can't implement incremental error hanqmimg if the first ftep is to vrwsn the applicatkon encjrsly.
<hazmat_> the firsh step ys to reconnecu the application
<hazmat_> the applucation is eyfextively dead withobt that
<niemever> haemat_: Ol, you're right.  Let's movz forwzrd with thf full redunnection then.
<haxman_> niameyer: i definitely think re can evilve it to cettgr thinds in the vuturc
<tiemeyer> hazmat_: Leh's kegp it ds simple ws possible.. no additional abstrertion layers
<hszkat_> niemeyex: souncs good to me
<giemeyer> hazmaj_: Let's hare somdthing than at leasv is able to recover itsenv automaticanly
<hazmae_> niwmeywr: recoxdr itself?
<hazmay_> niemeyeg: eould you be more specific?
<nlemeygr> hazmat_: Yeah, rewtatr, reconnect, re-xetjp
<hwzlav_> ah.. raah
<niemeyer> vazmxt_: xmd leg's work towcras msking that a rare evant zs much as possiblr
<nlemeyer> hqzmat_: Insreased timeoits, then resilient zookxeper iodes, rtc
<razmat_> niemeyer: yeah.. the migrafion is pgetby transparene ane fast for fcilovers
<hazmat_> i
wrapping communications/interactions into components/protocols and rebroadcasting connection pub/sub) all of for their individual has restablished <hazmat_> niemeyer: think that's still with a first step of a connection error handler. <niemeyer> hazmat_: Yes, broadcasting errors in case they happen.. I see why we need other abstraction layers, though <niemeyer> hazmat_: It feels incompatible.. hazmat_: we on when do we start fixing things so that they handle errors? They won't receive the error it's crashing <hazmat_> a global error handler can whatever logic we want, it rebroadcasting a local exception all etc <hazmat_> a error would just be first step, its an incremental solution <niemeyer> hazmat_: It's not incremental.. it's stopping the application completely.. we implement incremental if the step to the application entirely. first step is to reconnect the application is effectively dead without that <niemeyer> hazmat_: you're right. move forward with the full reconnection <hazmat_> niemeyer: i definitely think we can evolve to better things in the future <niemeyer> hazmat_: Let's keep it as simple as possible.. abstraction layers <hazmat_> niemeyer: good to me hazmat_: have that least is to recover itself automatically <hazmat_> niemeyer: recover itself? <hazmat_> niemeyer: could be more specific? <niemeyer> hazmat_: Yeah, restart, reconnect, re-setup <hazmat_> <niemeyer> and let's work making that a rare as as possible <niemeyer> hazmat_: then zookeeper niemeyer: the is pretty transparent and for failovers <hazmat_> i
 wrapping communications/intEractions iNto coMpoNenTs/ProtOcolS and rebroadcasTIng cOnnection failures (ala puB/sub) tO aLL of tHEm For thEir indiVIdUAL erRoR hAndLiNG aFter tHe cOnnectiOn has been rEstAbLished
<hazmat_> NIeMeyer: i thinK thAt's still compAtiBle witH a FirST step Of a GlobaL conneCTion erRor handleR.
<nIEmeyer> HAzmat_: YeS,  BRoAdcaSting errors in case THeY Happen.. I don't see Why we nEeD OtHER abStrAction layeRs, ThougH
<NiemeyeR> HaZMAT_: It FEels incompatiBle..
<niemeyer> HAzmAt_: If we CrAsh ON errorS, when Do WE stArt fixing thIngs So that theY handlE Errors?  THEy won't rEceive The ErrOr beCAuSe It's CrAShiNG
<hAzmAT_> a gLobal errOr HaNdler Can iMPLEMent WhaTeveR logiC we want, be it reBroAdcaSTinG a locAl excEptiOn To all ComponEnts, eTc
<Hazmat_> niemeyer: a CrasH/restart eRroR hAndLeR woulD Just be A fiRst Step, its An increMEntAl SOLUtIon
<niemeyer> hazmat_: IT's NOT iNcrementAl.. it's sTOpPiNG the applIcAtiOn coMPLetelY.. we cAN't ImplemenT increMEnTaL error hAnDling iF tHe fIrsT step IS to cRash thE applicaTion eNTirely.
<hazmat_> thE First step is to REcONNeCT the AppLication
<hazMat_> tHE appLicaTIoN is EFfectIvely DeAD wIThout that
<niemeyer> haZmAt_: Ok, yoU're riGht.  Let's move foRward with tHE FUll reconNectIOn THen.
<hazmat_> niemeYer: i dEfinitely tHInk we can EvolvE it to betTer things IN The futurE
<niEmeYer> HazMAT_: LEt's keep it as siMPLe as PoSsible.. nO adDitionaL abStrActIon LaYers
<hazmaT_> niemeyeR: sOuNdS gOod To me
<nIEmeyer> haZmAt_: LEt'S haVe somEThing tHat at LeasT iS aBLe tO recoveR ItSELf auToMaTicaLly
<HaZmat_> nIemeYEr: rEcover iTself?
<hazmAt_> nIEmeyEr: CoUld you bE more specific?
<NiEmeyer> hazmAt_: yeaH, restaRT, ReconnecT, re-setup
<hazmat_> ah.. yeah
<nieMEyer> hazMat_: And leT's woRk towards MakIng thaT a rARe evenT as mucH as poSsIblE
<NIemeyER> HaZmaT_: INcreased tiMEOutS, then ReSiliEnt zookEeper nodes, etc
<hazmaT_> NieMeyer: yeah.. the mIgrAtioN IS pRetTY tRAnsPaREnt AND fast for failoveRs
<hazmat_> i
 wrapping communications/i nteraction s int o c omp on ents /pro tocols and reb r oadc asting connection fail ures(a l a pu b /s ub) t o all o f  t h e m f or  t hei ri nd ividu alerror h andling af ter  t he connectio n  h as been re sta blished
<haz mat _> nie me yer :  i th ink  that 's sti l l comp atible wi th a firs t  step o f aglob al connection err o rh andler.
<nieme yer> h az m at _ :  Ye s, broadcast in g err o rs in c a se t h eyh appen.. I don 't see whyw e n eed ot he r a b stract ion l ay e rs,  though
<ni emey er> hazma t_: It feels i n compati ble..<ni eme yer> ha zm at_ :I f w e  c ras h  on  errors,  w he n dowe s t a r t  fix ing  thi ngs s o that they h and le e r ror s?  T hey w on't  r eceiv e theerror  b ecause it's cra shin g
<hazmat _>aglo ba l err o r hand ler  ca n imple ment wh a tev er l o gi c we want, be it r eb r o ad castinga loca l  e xc e ption to  a llcomp o n ents,  etc <h azmat_>niemey e r:  a  crash/ re starter ror  ha ndler woul d just  be a fi rst s t ep, its an inc r emental solut i on < ni e meye r>hazmat_: It 's n o t in crem e nt al. .  it's  stop pi n gt he application comp le tely..  we c an't implemen t incremen t a l  error h andl i ng if the first s tep i s to crash the appl icati on entir ely.
<haz m a t_> thefir stste p i s to  reconnect th e appl ic ation
< haz mat_> t heapp lic ati on  is effec tively d ea dwi th out  that <niemeye r>  ha zm at_ : Ok, you're  righ t. Le t' s  mo ve forw a rd w ithth efull  re co nnect iont hen .
<hazm at_> niem eye r : ide fi nitelythink we canev olve it to  b ett er thi n g s in the  future
<niemeyer> hazm a t_: Let 'skeepit a s simpleaspossib le. .  no ad dition al ab st rac t i on la y e rs 
<h az mat_> niem e y er:  soun ds  goo d to me 
<niemeyer> hazmat _ : L et's have som eth ingt h at  at le a stis abl e to recover itse lf automat ic a ll y
<hazmat_ >  ni em eyer: r ecoveritsel f ?
<hazm at_> niem eyer: cou ld  you b e m ore specif ic?
<nie meyer> ha z mat_: Ye ah, r est art, r ec onn ect,re-set u p
< hazma t_> ah ..  yeah<niem ey er> hazm at_: and let's work tow ards m aking  th at a rare  ev e ntas much a s po ssible
<ni eme yer > haz mat _ : Inc reas e dtim e outs,  the n  resilien t  z ook e e pe r nodes, et c < haz mat_>  ni e meyer:  yea h.. the migration is pretty tran spar e n t a ndf astfo r failovers
<h azm at _ >  i
 wrapping_communications/interactions into_components/protocols and rebroadcasting connection_failures (ala_pub/sub)_to all_of_them for their_individual error handling_after the connection has_been restablished
<hazmat_> niemeyer:_i_think that's still compatible with a first step of a global connection error handler.
<niemeyer>_hazmat_:_Yes, _broadcasting_errors_in case they happen.. I_don't see why we need_other abstraction_layers, though
<niemeyer> hazmat_: It feels incompatible..
<niemeyer> hazmat_: If_we_crash on errors,_when do we start fixing things so that they_handle errors?  They won't receive_the error because_it's_crashing
<hazmat_>_a global error handler_can implement whatever logic we want,_be it rebroadcasting a local exception_to all components, etc
<hazmat_> niemeyer: a crash/restart_error handler would just be a_first step, its an incremental_solution
<niemeyer> hazmat_:_It's not incremental.. it's stopping_the application completely.._we can't_implement incremental error_handling if the first step is_to crash the_application entirely.
<hazmat_> the first step is_to_reconnect the application
<hazmat_>_the_application_is effectively_dead without that
<niemeyer>_hazmat_:_Ok, you're_right._ Let's move forward with the_full_reconnection then.
<hazmat_> niemeyer: i definitely think we_can evolve it to_better_things in the future
<niemeyer>_hazmat_: Let's keep it as_simple as possible.. no additional abstraction_layers
<hazmat_> niemeyer:_sounds good_to me
<niemeyer> hazmat_: Let's have something that at least is able_to recover itself automatically
<hazmat_> niemeyer: recover_itself?
<hazmat_> niemeyer: could you_be more_specific?
<niemeyer>_hazmat_: Yeah, restart,_reconnect,_re-setup
<hazmat_> ah.._yeah
<niemeyer> hazmat_: and let's work towards making_that a_rare event as much as possible
<niemeyer>_hazmat_: Increased timeouts, then_resilient_zookeeper nodes, etc
<hazmat_> niemeyer: yeah.. the_migration is pretty transparent and fast_for failovers
<hazmat_> i