Lookup Error Failed to match node

nekkalapudi · Post by **nekkalapudi** » Wed Aug 02, 2006 1:38 pm

Hi,

Created and used Lookup fileset using same configuration file:
Failed to match node node2 (fastname colo-ascential-01) for LUT Fileset /opt/ds/dsdata/DEV/filesets/invmstr_lkup.fs

Checked the forum and tried setting Preserve Partition flag to Clear.
Still it's not working.

any one have some info...

Thanks

dsdesigner · Post by **dsdesigner** » Wed Aug 02, 2006 5:16 pm

Is your node 2 working properly? I remember once when we had this issue, we were told it was because of a problem with the node and it had to be removed from the config file node pool. Creating a new config by eliminating this node got rid of the problem. i think it's worth a try.

HTH.

kumar_s · Post by **kumar_s** » Wed Aug 02, 2006 11:05 pm

What is the partition used while creating the lookup fileset and what is used while doing a lookup?

ray.wurlod · Post by **ray.wurlod** » Wed Aug 02, 2006 11:11 pm

Given that the original post specified "same configuration file" I guess the question is whether the job that populated the Lookup File Set used the default node pool or was constrained to operate in a particular node pool at that time.

However, it's much more likely that there is a problem with node #2 (which, remember, is the third processing node named in the configuration file; numbering is zero-based).

kumar_s · Post by **kumar_s** » Thu Aug 03, 2006 1:32 am

Check whether the file is been written under each node pool.
Try to recreate with another set of config file and try to do a lookup.

nekkalapudi · Post by **nekkalapudi** » Mon Aug 14, 2006 12:24 pm

kumar_s wrote:Check whether the file is been written under each node pool.
Try to recreate with another set of config file and try to do a lookup.

Hi All,

Sorry for the late follow up.
I checked all the conditions and recreated the new file set and used. Still has the same problem. Did more investigation; actually I am doing aggregation before lookup and feeding the output of aggregation to lookup stage. Before aggregation the data was hashed and partitioned. This was causing problem. Resolved issue by setting aggregator stage preserves partition value to clear.
Thanks for your time and advice.