I'm using restmq as intermediate queue feeding it data from collectd and then popping and formating data and sending to OpenTSDB.
The docs say that a GET on the /q/<queue> route will return and dequeue the object. I see from the raw network traffic that restmq does RPOP on collectd_data:queue and hence removes the reference to the object. It does not however remove the actual object which will live on in memory forever.
I see in the source that the JSON interface has a take command which should GET and DEL the actual object. But I'm only getting 400 errors on the /queue route.
The docs say that the route is /queue/<queue_name>, which is incorrect. The route is /queue and the queue_name should be supplied in the JSON data.
I use this command to try to get the JSON interface to work without success:
curl -H "Accept: application/json" -H "Content-type: application/json" -X POST -d '{"cmd": "take","queue": "collectd_data"}' http://localhost:8888/queue
I'm using restmq as intermediate queue feeding it data from collectd and then popping and formating data and sending to OpenTSDB.
The docs say that a GET on the
/q/<queue>route will return and dequeue the object. I see from the raw network traffic that restmq does RPOP oncollectd_data:queueand hence removes the reference to the object. It does not however remove the actual object which will live on in memory forever.I see in the source that the JSON interface has a
takecommand which should GET and DEL the actual object. But I'm only getting 400 errors on the/queueroute.The docs say that the route is
/queue/<queue_name>, which is incorrect. The route is/queueand the queue_name should be supplied in the JSON data.I use this command to try to get the JSON interface to work without success: