> On May 1, 2017, at 2:41 PM, Aashish Sharma wrote:
>
>
>>const global_hash_seed: string = ""
>
> Yes, with setting of global_hash_seed, bloomfilter movement across workers is
> working fine and as expected, I see from initial tests.
Speaking of this, I think we still
> const global_hash_seed: string = ""
Yes, with setting of global_hash_seed, bloomfilter movement across workers is
working fine and as expected, I see from initial tests.
While we are on this thread, is the following good or there is a better way to
copy/merge bloomfilter once its sent
On Mon, May 01, 2017 at 08:20 -0700, you wrote:
> Actually - I am not sure if we ever implemented consistent hashing over the
> cluster;
Ah, good point, we did implement that, but it needs to be configured:
## Seed for hashes computed internally for probabilistic data structures.
Using
>> 1493427133.170419 Reporter::ERROR incompatible hashers in
>> BasicBloomFilter merge (empty) -
>
>> Not sure if the error is because an opaque of bloomfilter cannot be
>> sent over worker2manager_events and manager2worker_events or if I am
>> doing something not quite right.
>
> Bloom
On Fri, Apr 28, 2017 at 17:55 -0700, you wrote:
> 1493427133.170419 Reporter::ERROR incompatible hashers in
> BasicBloomFilter merge (empty) -
> Not sure if the error is because an opaque of bloomfilter cannot be
> sent over worker2manager_events and manager2worker_events or if I am
>