Re: error from HelixStateTransitionHandler

2016-04-25 Thread Neutron sharc
25 20:13:48,573 >> org.apache.helix.messaging.handling.HelixStateTransitionHandler:385] >> Skip internal error. errCode: ERROR, errMsg: Current state of >> stateModel does not match the fromState in Message, Current >> State:MASTER, message expected:SLAVE, partition: P

Re: error from HelixStateTransitionHandler

2016-04-25 Thread kishore g
_0, from: > host1_admin, to: host1_disk1 > > [ERROR 2016-04-25 20:13:48,577 > org.apache.helix.messaging.handling.HelixStateTransitionHandler:385] > Skip internal error. errCode: ERROR, errMsg: Current state of > stateModel does not match the fromState in Message, Current

Re: error from HelixStateTransitionHandler

2016-04-25 Thread Neutron sharc
ROR 2016-04-25 20:13:48,594 org.apache.helix.messaging.handling.HelixStateTransitionHandler:385] Skip internal error. errCode: ERROR, errMsg: Current state of stateModel does not match the fromState in Message, Current State:MASTER, message expected:SLAVE, partition: Pool0_1, from: host1_admin, to

Re: error from HelixStateTransitionHandler

2016-04-23 Thread kishore g
How many resources do you have. Partition names must be unique across the entire cluster. Can you also paste the idealstate for the resources On Sat, Apr 23, 2016 at 10:39 PM, Neutron sharc wrote: > Hi Helix team, > > I keep seeing this error from HelixStateTransitionHandler when th

error from HelixStateTransitionHandler

2016-04-23 Thread Neutron sharc
Hi Helix team, I keep seeing this error from HelixStateTransitionHandler when the state machine is running. It seems a partition's actual state doesn't match with the state marked in controller message. What are the usual causes? I'm using helix 0.7.1. Here is m