Two GetHDFS processors, each with different Hadoop Configuration Resources, will only operate with one Hadoop cluster. In this specific case, both Hadoop clusters had the same HDFS system name. The AbstractHadoopProcessor disables caching of Configuration and FileSystem objects but it doesn't appear to be working.
Also, if I configure a GetHDFS processor to point to one Hadoop cluster, but the processor is invalid because the Directory doesn't exist, the processor doesn't start (that's good). But if I change the Hadoop Configuration Resources to point to a different Hadoop cluster where the Directory does exist, then GetHDFS continues to talk to the first Hadoop cluster. It seems like the Configuration and FileSystem objects don't reset when I change the Hadoop Configuration Resources property.