ashwinraghav
commented
11 years ago We do care about bursts for all notifications. How does the definition of a Burst change because of concurrent writes. We are going to tell a client that he will not receive notifications for a fixed period after the burst notification. Otherwise, we cannot scale this system. Once the client knows that he will not receive notifications for a fixed period, he can take alternate actions like invalidating his cache for that period etc
tjt7a
In its current state, the BurstController will call a series of notifications a BURST if notifications arrive within a period of .
The question is, do we care about the type of notifications? Do we consider Read->Write->Read->Write->... to be considered a Burst as much as Write->Write->Write->Write->...?
I think it is possible that with enough clients looking at the same file, having many reads/writes to the same file is reasonable and not BURST behavior.