I solved the problem my self. It was due too the fact my own Writables had some serialization problems (Null pointers when reading back to an object which I instantiated incorrectly). The reason I point this out, is that it did not stop the program from running. Shouldn't such an error stop the program entirely? Since no messages could be received because of it, the program has no need to run any further.
On Thu, Oct 31, 2013 at 10:37 AM, Steven van Beelen <[email protected]>wrote: > To make my question more clear, this is what it boils down to: > > "Message loss when running in distributed mode" > > Could someone gave me a small clue why this could happen? > > > On Wed, Oct 30, 2013 at 1:31 PM, Steven van Beelen > <[email protected]>wrote: > >> Hi, >> >> One of my programs works perfectly fine in local mode, but once I run it >> in distributed mode I seem to lose the messages send between peers. >> The system notes I have send messages (logs), the peers they send to >> exist (peer name is selected correctly), but they never arrive on the >> receiving peer side. The local mode does not have this issue and works >> perfectly fine. Additionally, other Hama programs I created do not have >> this issue on the same cluster. >> >> Has someone experienced this problem as well or could anyone give me >> pointers what to do? >> >> Regards, >> >> Steven >> > >
