-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathNUMSUB_print.txt
84 lines (66 loc) · 3.25 KB
/
NUMSUB_print.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
Config :
3 nodes pub to redis-1
0 nodes pub to redis-2
0 nodes pub to redis-3
node-2 | Receive event : get_all_rooms
node-2 | NUMSUB : 0
node-2 | Error: timeout reached while waiting for allRooms response
node-2 | at Timeout._onTimeout (/app/socket.io-redis/index.js:546:48)
node-2 | at listOnTimeout (internal/timers.js:531:17)
node-2 | at processTimers (internal/timers.js:475:7)
node-2 | [ '/admin#uJFOAsn4D1VOoffZAAAA', 'room1' ]
node-2 | Receive event : get_all_rooms
node-2 | NUMSUB : 3
node-2 | [ '/admin#uJFOAsn4D1VOoffZAAAA', 'room1' ]
node-2 | Receive event : get_all_rooms
node-2 | NUMSUB : 0
node-2 | Error: timeout reached while waiting for allRooms response
node-2 | at Timeout._onTimeout (/app/socket.io-redis/index.js:546:48)
node-2 | at listOnTimeout (internal/timers.js:531:17)
node-2 | at processTimers (internal/timers.js:475:7)
node-2 | [ '/admin#uJFOAsn4D1VOoffZAAAA', 'room1' ]
node-2 | Receive event : get_all_rooms
node-2 | NUMSUB : 0
node-2 | Error: timeout reached while waiting for allRooms response
node-2 | at Timeout._onTimeout (/app/socket.io-redis/index.js:546:48)
node-2 | at listOnTimeout (internal/timers.js:531:17)
node-2 | at processTimers (internal/timers.js:475:7)
node-2 | [ '/admin#uJFOAsn4D1VOoffZAAAA', 'room1' ]
node-2 | Receive event : get_all_rooms
node-2 | NUMSUB : 0
node-2 | Error: timeout reached while waiting for allRooms response
node-2 | at Timeout._onTimeout (/app/socket.io-redis/index.js:546:48)
node-2 | at listOnTimeout (internal/timers.js:531:17)
node-2 | at processTimers (internal/timers.js:475:7)
node-2 | [ '/admin#uJFOAsn4D1VOoffZAAAA', 'room1' ]
=> If the numsub happens on redis-1 it's ok, else => timeout !
Config :
0 nodes pub to redis-1
1 nodes pub to redis-2
2 nodes pub to redis-3
-> numsub redis-1 :
node-2 | Receive event : get_all_rooms
node-2 | NUMSUB : 0
node-2 | Error: timeout reached while waiting for allRooms response
node-2 | at Timeout._onTimeout (/app/socket.io-redis/index.js:546:48)
node-2 | at listOnTimeout (internal/timers.js:531:17)
node-2 | at processTimers (internal/timers.js:475:7)
node-2 | [ '/admin#Q1aGVLTSPnAavLcEAAAA', 'room1' ]
-> numsub redis-2 :
node-2 | Receive event : get_all_rooms
node-2 | NUMSUB : 1
node-2 | []
-> numsub redis-3 :
node-2 | Receive event : get_all_rooms
node-2 | NUMSUB : 2
node-2 | []
-> numsub redis-3
node-2 | Receive event : get_all_rooms
node-2 | NUMSUB : 2
node-2 | [ '/admin#Q1aGVLTSPnAavLcEAAAA', 'room1' ]
--> sometimes it's ok even if the numbsub is false
--> It takes the 2 firts to reply ! So by luck it can be good !
1569088149.532803 [0 192.168.96.7:44426] "pubsub" "numsub" "socket.io-request#/admin#"
1569088149.533499 [0 192.168.96.7:44426] "publish" "socket.io-request#/admin#" "{\"requestid\":\"CruwvB\",\"type\":2}"
1569088149.534067 [0 192.168.96.7:44426] "publish" "socket.io-response#/admin#" "{\"requestid\":\"CruwvB\",\"rooms\":[\"/admin#Q1aGVLTSPnAavLcEAAAA\",\"room1\"]}"
1569088149.535536 [0 192.168.96.8:50082] "publish" "socket.io-response#/admin#" "{\"requestid\":\"CruwvB\",\"rooms\":[]}"