# Storage process being assigned log roles automatically **URL:** \ **Category:** Running FoundationDB\ **Created:** [June 8, 2020, 10:53am UTC](https://forums.foundationdb.org/t/storage-process-being-assigned-log-roles-automatically/2170 "2020-06-08T10:53:48Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![gaurav](https://avatars.discourse-cdn.com/v4/letter/g/b487fb/32.png) [@gaurav](https://forums.foundationdb.org/u/gaurav)\ **Post date:** [June 8, 2020, 1:19pm UTC](https://forums.foundationdb.org/t/storage-process-being-assigned-log-roles-automatically/2170/2 "2020-06-08T13:19:28Z")
How many tlogs are there in the cluster - probably 3+ due to triple replication ? There appears to be only a single fdb process with log class; so if there are more tlogs then they will go to other fdbservers. From what you’ve configured, `storage` seems like the next best alternate class for them. See this post for more details: > [@Roles / Classes matrix](https://forums.foundationdb.org/t/roles-classes-matrix/1340): > > Hi All, based on suggestions from a github issue, I am posting a visual representation of class/roles fitness matrix, and fitness ordering matrix: @alexmiller @ajbeamon going through this matrix again, a few questions came up that I had probably not thought about earlier: How does FDB decide how many SS to recruit in the cluster? Will it try to recruit one SS on each process class where it is allowed to do so (that is everything except for those with NeverFit)? Specifically, will … --- _[View the full topic](https://forums.foundationdb.org/t/storage-process-being-assigned-log-roles-automatically/2170)._