Jia Zhai 2017-09-13, 01:16
  Enrico Olivelli 2017-09-05, 20:13
  Sijie Guo 2017-09-05, 19:28
  Jia Zhai 2017-09-06, 00:23
  Enrico Olivelli 2017-09-06, 17:51
  Sijie Guo 2017-09-06, 20:24
  Enrico Olivelli 2017-09-06, 20:07
  Enrico Olivelli 2017-09-06, 11:57
  Sijie Guo 2017-09-06, 16:25
  Enrico Olivelli 2017-09-05, 13:31
  Jia Zhai 2017-09-05, 13:10
  Jia Zhai 2017-09-07, 01:45
  Jia Zhai 2017-09-12, 08:30
  Enrico Olivelli 2017-09-16, 10:17
  Jia Zhai 2017-09-16, 10:10
  Venkateswara Rao Jujjuri 2017-09-16, 22:52
  Sijie Guo 2017-09-18, 23:08
  Enrico Olivelli 2017-09-13, 07:16
  Sijie Guo 2017-09-13, 08:10
2017-09-13 10:10 GMT+02:00 Sijie Guo <[EMAIL PROTECTED]>:
Yep, we are on the same page
for this proposal the bookie will be a sort of "proxy" between the client
and the actual ledger manager implementation which will "live" inside the
it is only a new ledger manager to be used in clients, this ledger manager
will issue RPCs (or kind of "streaming" RPCs) to a list of bookies

Sorry. Maybe my curiosity is not clear.
If you have multiple bookies and each bookie holds its own version of
metadata, how do you coordinate them ? which will be the source of truth ?
Maybe we should start a new email thread in the future to talk about
"alternative distributed metadata storages"

Any way the meaning and the scope of the proposal is clear to me and I am
really OK with it, I hope it will get soon approved

-- Enrico
  Sijie Guo 2017-09-13, 08:25
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB