Hi,
How does Hedwig handles this scenario? Since only one of the hubs have the
ownership of a topic, the same hub is able to serve both publish and subscribe
requests concurrently. Is my understanding correct ?
Also, what is the purpose of ReadAheadCache class in Hedwig? Is it used
somewhere
I thought we had agreed at some point that the application should do it in the case it needs this feature. That is, every so often the app writer either writes to ZooKeeper its last confirmed write or it sends directly to the reader. Knowing a confirmed write x enables the reader to read up to
in hedwig one hub does both the publish and subscribe for a given
topic and therefore is the only processes reading and writing from/to a
ledger, so there isn't an issue.
The ReadAheadCache does read-ahead :) it is so that we can minimize
latency when doing sequential reads.
ben
On
