Hi Guys,
I'm getting problem from my workers:
*Java8 / Storm 1.0.1 / Fedora24*
I'm constantly get worker restarted (their GUID changes in logs) with the
following exception:
Caused by: java.lang.ClassNotFoundException:
backtype.storm.messaging.netty.Context
at java.net.URLClassLoader.findCl
Not the frameworks but applications running on the framework. I am talking
about the rolling upgrade of a topology (not the entire cluster). Similar
to blue green deployments of microservices
On Aug 26, 2016 9:35 PM, "Harsha Chintalapani" wrote:
> Abhishek,
> Are you looking rolling upgr
I am running Storm 0.9.6 on a two-node cluster: one nimbus/ui server
and one supervisor server.
I am getting the error below, and I cannot install topologies. The
error happens over and over.
I have tried:
* Resetting the zookeeper cluster
* Wiping out the content of the storm lo
Abhishek,
Are you looking rolling upgrade kafka cluster or storm?
Harsha
On Fri, Aug 26, 2016 at 6:18 AM Abhishek Agarwal
wrote:
>
> On Aug 26, 2016 2:50 PM, "Abhishek Agarwal" wrote:
>
> >
>
> > Here is an interesting use case - To upgrade a topology without any
> downtime. Let's say,
On Aug 26, 2016 2:50 PM, "Abhishek Agarwal" wrote:
>
> Here is an interesting use case - To upgrade a topology without any
downtime. Let's say, the topology has only Kafka as a source and two
versions of it are running (different topology names of course) in parallel
and sharing the kafka input
Hi all,
I've been using Flux to configure my topologies, but have noticed that it
doesn't let you specify the number of tasks against executors- only a
parallelism hint.
When previously configuring topologies using code, you could set the number
of executors, and then specify the number of tasks
Here is an interesting use case - To upgrade a topology without any
downtime. Let's say, the topology has only Kafka as a source and two
versions of it are running (different topology names of course) in parallel
and sharing the kafka input load.
In old kafka spout, rolling upgrade is not possible
