Con Kolivas
|
a7da93981e
|
Determine whether we need to reconnect clients based on the parent proxy's notify id which is reset on each subscribe
|
10 years ago |
|
Con Kolivas
|
5dc3f9cb22
|
Only issue reconnect when the parent pool has set its notified flag
|
10 years ago |
|
Con Kolivas
|
5cb12347a7
|
Add parent proxy as a subproxy in stratifier
|
10 years ago |
|
Con Kolivas
|
c8025958f9
|
Add notify and diff subid details
|
10 years ago |
|
Con Kolivas
|
371b59f452
|
Use a different hashlist for the subproxies in the stratifier to avoid hashlist clash
|
10 years ago |
|
Con Kolivas
|
d0f557bbf8
|
Handle reconnect message differently for parent proxy than child subproxies
|
10 years ago |
|
Con Kolivas
|
aa153ba742
|
Differentiate pong from other spurious messages from clients
|
10 years ago |
|
Con Kolivas
|
df1465f275
|
Use msg_id variable for clarity
|
10 years ago |
|
Con Kolivas
|
338cc49c7e
|
Add verbose notify message
|
10 years ago |
|
Con Kolivas
|
9b04f81666
|
Set correct variable in update_diff
|
10 years ago |
|
Con Kolivas
|
f15fbdbc70
|
Receive diff from the upstream proxy and add share submission to the correct psend list
|
10 years ago |
|
Con Kolivas
|
955bbe6977
|
Use the client's sdata to associate correct share submissions with the upstream proxy
|
10 years ago |
|
Con Kolivas
|
6a21a67c1e
|
Use client sdata with update_client call
|
10 years ago |
|
Con Kolivas
|
319d0943fc
|
Update diff on all stratifier data but send diff only to clients bound to the current subproxy
|
10 years ago |
|
Con Kolivas
|
bcd499bf31
|
Assign the client subproxy data in new_enonce1
|
10 years ago |
|
Con Kolivas
|
c872ce9de8
|
Store the proxy and subproxy id only in clients and sort subproxies by subid to avoid confusion
|
10 years ago |
|
Con Kolivas
|
dc293beb9c
|
Separate delivery of messages by ckpool sdata and per proxy sdata
|
10 years ago |
|
Con Kolivas
|
dd1dae4ae3
|
Send the relevant sdata to be used by new_enonce1
|
10 years ago |
|
Con Kolivas
|
7763b49c2e
|
Allow stratifier to choose the best subproxy to attach new users to and request recruitment of more subproxies when the headroom for more clients is low
|
10 years ago |
|
Con Kolivas
|
6822282672
|
Generate stratifier data per subproxy instead of per proxy since they'll have unique workbases
|
10 years ago |
|
Con Kolivas
|
d62483fbd2
|
Workbases always exists by the time we reach the point we can set the enonce2varlen
|
10 years ago |
|
Con Kolivas
|
03712fe2d7
|
Broadcast data according to the sdata it belongs to
|
10 years ago |
|
Con Kolivas
|
b1f92414c5
|
Store which sdata each client is bound to
|
10 years ago |
|
Con Kolivas
|
e360a9842b
|
Add the workbase to each unique sdata as required
|
10 years ago |
|
Con Kolivas
|
ba910251da
|
Choose the sdata to use by subproxy
|
10 years ago |
|
Con Kolivas
|
1f83be877d
|
Send subproxy id when setting proxy at stratifier and set the current proxy to the subproxy instead of the master proxy
|
10 years ago |
|
Con Kolivas
|
b77027b09c
|
Create a unique stratifer data structure per subproxy
|
10 years ago |
|
Con Kolivas
|
d05db855ff
|
Create infrastructure for a list of subproxies per proxy and generating them
|
10 years ago |
|
Con Kolivas
|
08e47d28cf
|
Give each proxy an enonce1 union and cap the handout of enonce1 values without repeating, assuming we will recruit more proxied connections upstream to compensate
|
10 years ago |
|
Con Kolivas
|
e986c04c68
|
Fix non proxy mode breakage
|
10 years ago |
|
Con Kolivas
|
3b40b805bd
|
Store the proxy and subproxy id work is generated from
|
10 years ago |
|
Con Kolivas
|
abde70a8d9
|
Store the id and subid of the proxy in use by each client, submitting the value with its shares to the generator
|
10 years ago |
|
Con Kolivas
|
26c890c291
|
Send the diff from the proxy instance as soon as we get it and differentiate which proxy it comes from
|
10 years ago |
|
Con Kolivas
|
ab4d3a672f
|
Set notified flag to false immediately upon setting a new proxy
|
10 years ago |
|
Con Kolivas
|
64a3703f09
|
Move to pushing all notify data from the generator to avoid an extra message and reconnect clients once the current proxy has its first notification data
|
10 years ago |
|
Con Kolivas
|
836f2f3ff2
|
Avoid extra call to get subscription from generator by pushing it with the subscribe message to the stratifier
|
10 years ago |
|
Con Kolivas
|
db9a777767
|
Reconnect clients lazily on proxy switch once we receive another message from them and drop them if they don't disconnect on their own within a minute
|
10 years ago |
|
Con Kolivas
|
a80f9aa492
|
Don't miss dropping stratifier clients whose dropped flag is set when no reference count is held
|
10 years ago |
|
Con Kolivas
|
f0f628df84
|
Reuse known ckp variable in drop_client
|
10 years ago |
|
Con Kolivas
|
c5b856ac7c
|
Update notify after setting proxy before reconnecting clients
|
10 years ago |
|
Con Kolivas
|
32b88de36c
|
Explicitly set the proxy in the stratifier when we switch and avoid creating workbases from backup proxies
|
10 years ago |
|
Con Kolivas
|
042360bf40
|
Don't try to act on inactive clients
|
10 years ago |
|
Con Kolivas
|
14e3ed70c8
|
Don't try to act on inactive clients
|
10 years ago |
|
Con Kolivas
|
5a19bd0e4a
|
Send a reconnect if we detect a changed subscription on the current proxy
|
10 years ago |
|
Con Kolivas
|
57e7916296
|
Demote unnecessary warning in stratifier to debug
|
10 years ago |
|
Con Kolivas
|
d02862d1fe
|
Update subscriptions and notifications for proxies that aren't the current proxy for faster switching
|
10 years ago |
|
Con Kolivas
|
520b36cc70
|
Send which proxy we wish to get a subscribe or notify to/from the connector to stratifier and whether to reconnect
|
10 years ago |
|
Con Kolivas
|
f02a35dfcf
|
Send notready message when notify data is not ready in the generator instead of no response
|
10 years ago |
|
Con Kolivas
|
b7e71e1be7
|
Attach to every upstream pool in proxy mode all the time and fail over and back as needed
|
10 years ago |
|
Con Kolivas
|
52cd066563
|
Add proxies to the stratifier as its notified of their existence by the generator and issue reconnects without rejecting connections when a new subscribe is discovered
|
10 years ago |
