Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
I came across a case where a tablet server had just about 2K live tablet replicas, but it opened about 24K files in its WAL and data directories. The issue stems from the fact that tombstoned tablet replica's files are opened by the FS manager the same as for a live replica, and those are kept open even if they are never about to change. It would be prudent to avoid keeping tombstoned tablet replicas' files open, if possible: maybe, just read the required information (last voted term and opId index?) and keep it in runtime structures, but close corresponding files right after bootstrapping?
Otherwise, this doesn't seem to scale well.
Attachments
Issue Links
- relates to
-
KUDU-3486 Tserver: Too many tombstone tablet may lead to high memory usage.
- Resolved