Can someone please provide postmas...@sas.sungardrs.com with directions
on how to unsubscribe? : )
-------- Original Message --------
Subject: DELIVERY FAILURE: The message could not be delivered because
the recipient's destination email system is unknown or invalid. Please
check the address and try again, or contact your system administrator to
verify connectivity to the email system of the recipient. [MAPI Reason
Code: 0, MAPI Diagnostic Code 48]
From: <postmas...@sas.sungardrs.com>
Date: Wed, August 15, 2012 6:53 pm
To: <jcfol...@pureperfect.com>
Your message
Subject: RE: OK to run data node on same machine as secondary name
node?
was not delivered to:
"NOTES:Stanislav_Seltser/SSP/SUNGARD%SSP-Bedford"@sas.sungardrs.com
because:
The message could not be delivered because the recipient's destination
email system is unknown or invalid. Please check the address and try
again, or contact your system administrator to verify connectivity to
the email system of the recipient. [MAPI Reason Code: 0, MAPI Diagnostic
Code 48]
Reporting-MTA: x-local-hostname; SUNGARD
Final-Recipient:
rfc822;"NOTES:Stanislav_Seltser/SSP/SUNGARD%SSP-Bedford"@sas.sungardrs.com
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Notes;The message could not be delivered because the
recipient's destination email system is unknown or invalid. Please check the
address and try again, or contact your system administrator to verify
connectivity to the email system of
--- Begin Message ---
Not an expert but... I think a lot of it depends on your usage pattern.
How many machines are we talking about? What is the replication factor?
If it's only two machines, there would need to be a datanode on both in
order to provide replication.
I guess you could also keep the secondary name node on the same machine
as the name node and just have the other(s) be a data node. After all,
that is the default configuration. It certainly makes administration
easier, since you would only need two machine images instead of three.
If the name node goes down you're hosed anyway. The down side would be
memory consumption on the name node, but recovery time would be faster.
It may not be the best configuration for write-heavy workloads and at
some point you are going to hit a hardware ceiling.
-------- Original Message --------
Subject: OK to run data node on same machine as secondary name node?
From: David Rosenstrauch <dar...@darose.net>
Date: Wed, August 15, 2012 6:11 pm
To: user@hadoop.apache.org
I have a Hadoop cluster that's a little tight on resources. I was
thinking one way I could solve this could be by running an additional
data node on the same machine as the secondary name node.
I wouldn't dare do that on the primary name node, since that machine
needs to be extremely performant. But since all the secondary name node
does is doing a merge of the name node's checkpoint and logs, which is
not an activity that require top-notch real-time performance, I thought
it might not be a problem if I were to set up a data node running there
as well.
Any reasons why that might be a bad idea?
Thanks,
DR
--- End Message ---
