Description
Now we are nesting DefaultWALProvider inside RegionGroupingProvider, which makes the logic ambiguous since a "provider" itself should provide logs. Suggest to directly instantiate FSHlog in RegionGroupingProvider.
W.r.t wal group name, now in RegionGroupingProvider it's using sth like "<factoryId>-null-<randomUUID>" which is quite long and unnecessary. Suggest to directly use "<providerId>.<groupName>".
For more details, please refer to the initial patch.
Attachments
Attachments
Issue Links
- breaks
-
HBASE-21843 RegionGroupingProvider breaks the meta wal file name pattern which may cause data loss for meta region
- Resolved
- Is contained by
-
HBASE-14457 Umbrella: Improve Multiple WAL for production usage
- Closed
- relates to
-
HBASE-14306 Refine RegionGroupingProvider: fix issues and make it more scalable
- Closed