> As far as I can tell, this is only an issue with the localBroker.  The
> HdfsBroker does not have this problem and I'm not sure about KFS
> (CloudStore).  The problem with this situation is that there is no graceful
> way to recover.  The operator needs to up the number descriptors and then
> restart the process.

Thinking more about it, you've made a good point and the existing
messages are sufficient.  I think the only remaining issue is that the
range server shouldn't segfault after the prolonged failures.  To me,
this suggests some sort of resource leak or improper cleanup that
should eventually be looked into for long-running processes.  I'll
open a ticket on this.

Thanks,

Eric
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Hypertable Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/hypertable-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to