Hi! It requires that data source of spout can replay datas which are from offset or read but not acked. For example, ack mode of rabbitmq holds datas which are read from subscriber, and rabbitmq removes data when data is acked. But when subscriber is disconnected, any datas which are not acked are available for read, which makes spout fault tolerant. If spout can handle data source offset instead of ack mode, spout may use ack / fail to adjust offset to achieve similar thing.
Hope this helps. Thanks! Jungtaek Lim (HeartSaVioR) 2015년 6월 7일 일요일, Chuanlei Ni<[email protected]>님이 작성한 메시지: > Hi, > Storm claims that it is robust even the node crushes. It is ok that > Nimbus can just restart to control the system, and the node just holds Bolt > can also ignore the issues. But if the spout crushes, and the `pending` map > data is lost. So the data lost. And some calculation would be not correct. > > Is there any mis-understand above? Just for discussion. > > Thanks > > Happy Weekends > > Chuanlei Ni > -- Name : 임 정택 Blog : http://www.heartsavior.net / http://dev.heartsavior.net Twitter : http://twitter.com/heartsavior LinkedIn : http://www.linkedin.com/in/heartsavior
