>>And before you suggest moving to NG, not an option at this time. Is upgrading to CDH3u4 an option?
http://www.cloudera.com/blog/2012/05/cdh3-update-4-is-now-available/ I'm not sure whether u4 will address the issue you're having, but at least I wanted to let you know it's available starting today. Cheers, Will On Wed, May 9, 2012 at 9:59 AM, Steve Hoffman <[email protected]> wrote: > I had setup 1 flow using flow isolation from several nodes to a single > collector (default port 35853). Things have been running just fine. > > When I added a second flow to the same collector, not only did the > second collector sink not receive any data, but the first went into > ERROR state (I assume because the first flow uses a different format > than the first and isn't written to deal with the second flow's > format). > > When I moved the second flow-id to another port (35854) my data came > thru which makes me believe you can't send different flow-ids to the > same collector port. That would seem very odd. After all, that is > the point of the flow identifier -- if I had to have a separate port > for every flow id, why bother with flow names? > > This is cloudera cdh3u3 flume (not NG). And before you suggest moving > to NG, not an option at this time. > > Thanks, > Steve >
