You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2020/02/19 08:52:49 UTC

[GitHub] [skywalking] wu-sheng edited a comment on issue #4131: ShardingSphere storage configuration, e2e test and doc for SkyWalking 7

wu-sheng edited a comment on issue #4131: ShardingSphere storage configuration, e2e test and doc for SkyWalking 7
URL: https://github.com/apache/skywalking/issues/4131#issuecomment-588105831
 
 
   > My first idea of sharding stratergy is to shard certain table, taking alarm_record for example, into 4 DBs and 10 tables each DB
   
   The number of shards is not the issue. My point is targeting which tables should be sharded. I don't like the idea we config them one by one. We could be use which tables are not sharded. Segment is a special case, and all others are metrics or related, so we could use the same rule for them.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services