Ankur Goel wrote:
What should happen ideally is when the namenode fails, secondary
namenode should automatically pickup from the last checkpoint without
hindering normal operations. The data-nodes should also detect this
change and upgrade their configurations accordingly. Not sure about the
behavior of JobTracker and TaskTracker in the middle of a running job.
I think we should have a separate jira for this.
I think a new feature to have a 'hot' or 'warm' replica of NameNode is
under the works. It does pretty much exactly what you want. Not sure
about more details or when the jira is going to be filed.
Raghu.
