bin/kafka-topics.sh --zookeeper localhost:2181 --list
bin/kafka-topics.sh --zookeeper localhost:2181 --describe --topic mytopic
bin/kafka-topics.sh --zookeeper localhost:2181 --alter --topic mytopic --config retention.ms=1000
... wait a minute ...
bin/kafka-topics.sh --zookeeper localhost:2181 --list
bin/kafka-topics.sh --zookeeper localhost:2181 --describe --topic mytopic
bin/kafka-topics.sh --zookeeper localhost:2181 --alter --topic mytopic --config retention.ms=1000
... wait a minute ...
#!/usr/bin/env python3 | |
# encoding: utf-8 | |
""" | |
I saw a similar script on the homepage of Miguel Grinberg (the Flask book guy), | |
but he was using webscraping. Here I use simple API calls instead. | |
The script takes the presentations of a Python conference and orders the | |
presentations in descending order by the number of youtube views. It | |
is an indicator about the popularity of a video. |
/** | |
* Google analytics include (using "Universal Analytics") | |
* https://gist.github.com/acusti/8718758 | |
*/ | |
/*global define */ | |
define(function(require) { | |
'use strict'; | |
RDBMS-based job queues have been criticized recently for being unable to handle heavy loads. And they deserve it, to some extent, because the queries used to safely lock a job have been pretty hairy. SELECT FOR UPDATE followed by an UPDATE works fine at first, but then you add more workers, and each is trying to SELECT FOR UPDATE the same row (and maybe throwing NOWAIT in there, then catching the errors and retrying), and things slow down.
On top of that, they have to actually update the row to mark it as locked, so the rest of your workers are sitting there waiting while one of them propagates its lock to disk (and the disks of however many servers you're replicating to). QueueClassic got some mileage out of the novel idea of randomly picking a row near the front of the queue to lock, but I can't still seem to get more than an an extra few hundred jobs per second out of it under heavy load.
So, many developers have started going straight t
# | |
# To check from where a maven dependency comes from | |
# | |
mvn dependency:tree -Dincludes=groupId:artifactId |