-
Notifications
You must be signed in to change notification settings - Fork 337
Problem getting data into skyline #92
Comments
On Mon, Jun 16, 2014 at 5:48 AM, detzom notifications@github.com wrote:
You're sure no data is sent to Redis? Have you done a keys *? "metrics. I'm not sure what the StringIO is doing, it looks like it may be a bug with Abe Stanway |
I checked my redis to ensure that no data is present : started with pid 22763 And it seems not :) |
Are you sure you're sending data? Have you tried running seed_data.py?
|
lol... Yes im totally sure :) and my server is plugged on ;) The last commit you pointed on seems to be the responsible, I reverted to previous one [root@skyline bin]# git status And now : started with pid 26713 127.0.0.1:6379> keys ?
So im really sending data, but last commit has broken TCP PICKLE reception from carbon-relay. |
This is my fault, missing dependencies. Fixing and committing now. |
detzom, if you could check the fix is working for you that would be most appreciated and I will close |
Fix is working great ;) No more problem with last commit, thank you ! |
Awesomesauce |
Hi everyone,
I made and update on my skyline, and now data are no more integrated on redis.
I used a version of skyline downloaded by zip, dont know which revision exactly, but certainly the state of 20/02/2014 skyline-master.
when I start OLD horizon.d I have the following in log :
started with pid 2644
2014-06-16 11:45:10 :: 2644 :: starting horizon agent
2014-06-16 11:45:10 :: 2645 :: started worker
2014-06-16 11:45:10 :: 2644 :: started roomba
2014-06-16 11:45:10 :: 2648 :: started listener
2014-06-16 11:45:10 :: 2648 :: listening over udp for messagepack on 2025
2014-06-16 11:45:10 :: 2647 :: started listener
2014-06-16 11:45:10 :: 2647 :: listening over tcp for pickles on 2024
2014-06-16 11:45:10 :: 2646 :: started worker
2014-06-16 11:45:10 :: 2650 :: operated on metrics. in 0.235132 seconds
2014-06-16 11:45:10 :: 2650 :: metrics. keyspace is 1003
2014-06-16 11:45:10 :: 2650 :: blocked 0 times
2014-06-16 11:45:10 :: 2650 :: euthanized 0 geriatric keys
2014-06-16 11:45:10 :: 2650 :: sleeping due to low run time...
2014-06-16 11:45:11 :: 2647 :: connection from xxxxxxxxxxx:2024
2014-06-16 11:45:11 :: 2645 :: queue size at 134
2014-06-16 11:45:11 :: 2645 :: queue size at 326
2014-06-16 11:45:11 :: 2645 :: queue size at 488
...
when I start CURRENT horizon.d (with exactly same settings.py) I have the following in log :
started with pid 2702
2014-06-16 11:46:56 :: 2702 :: starting horizon agent
2014-06-16 11:46:56 :: 2703 :: started worker
2014-06-16 11:46:56 :: 2705 :: started listener
2014-06-16 11:46:56 :: 2702 :: started roomba
2014-06-16 11:46:56 :: 2705 :: listening over tcp for pickles on 2024
2014-06-16 11:46:56 :: 2706 :: started listener
2014-06-16 11:46:56 :: 2706 :: listening over udp for messagepack on 2025
2014-06-16 11:46:56 :: 2704 :: started worker
2014-06-16 11:46:57 :: 2708 :: operated on metrics. in 0.263879 seconds
2014-06-16 11:46:57 :: 2708 :: metrics. keyspace is 1007
2014-06-16 11:46:57 :: 2708 :: blocked 0 times
2014-06-16 11:46:57 :: 2708 :: euthanized 0 geriatric keys
2014-06-16 11:46:57 :: 2708 :: sleeping due to low run time...
2014-06-16 11:46:58 :: 2705 :: connection from xxxxxxxxxx:2024
2014-06-16 11:46:58 :: 2705 :: global name 'StringIO' is not defined
2014-06-16 11:46:58 :: 2705 :: incoming connection dropped, attempting to reconnect
2014-06-16 11:46:58 :: 2705 :: listening over tcp for pickles on 2024
2014-06-16 11:47:07 :: 2713 :: operated on metrics. in 0.252194 seconds
2014-06-16 11:47:07 :: 2713 :: metrics. keyspace is 1007
2014-06-16 11:47:07 :: 2713 :: blocked 0 times
2014-06-16 11:47:07 :: 2713 :: euthanized 0 geriatric keys
2014-06-16 11:47:07 :: 2713 :: sleeping due to low run time...
2014-06-16 11:47:11 :: 2704 :: worker queue is empty and timed out
2014-06-16 11:47:11 :: 2703 :: worker queue is empty and timed out
...
And no data is sent to redis.
Should I come back to my old working skyline or there is some changes on horizon.d that explain the change of behaviour concerning TCP PICKLES data transfers ?
The text was updated successfully, but these errors were encountered: