[uWSGI] how to properly set nodes and udp in cache2 config

Lu Liu nudtlliu at gmail.com
Wed Oct 16 10:51:38 CEST 2013

Hi Roberto,

thanks a lot for your reply. I tried changing my config on slave to:

cache2 = name=test-conf-cache,items=8192,blocksize=2048,udp=

and on master to:

cache2 = name=test-conf-cache,items=8192,blocksize=2048,store=/shared_disk/test_cache2.dump,udp=,nodes=

After that, I start slave first, then the master. But this config even
can not make slave know the initial data stored in the dump file. And
the slave can not receive cache updates as before.

Then I tried change the slave config to:
cache2 = name=test-conf-cache,items=8192,blocksize=2048,store=/shared_disk/test_cache2.dump,udp=

the slave can load the initial data stored in dump file, but still can
not receive cache2 updates. I traced the count of cache keys in log,
and found the number does not change on slave even after ~15 mins that
master has added a new item. BTW, I use nginx as a backward proxy
which communicates with uwsgi via unix sockets. Does that matter? What
do I miss?



On Wed, Oct 16, 2013 at 11:50 AM, Roberto De Ioris <roberto at unbit.it> wrote:
>> Both server must bind to an address reachable by the other one.
>> A minimal example:
>> (slave udp on port 3030)
>> uwsgi -M --cache2 name=foo,items=100,udp= -s :3032
>> (master udp on port 1717, push to port 1717)
> here i mean "push to port 3030", sorry
> --
> Roberto De Ioris
> http://unbit.it
> _______________________________________________
> uWSGI mailing list
> uWSGI at lists.unbit.it
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

More information about the uWSGI mailing list