Closed nrc closed 5 years ago
Blog posts:
I think by the end of July we should have finished migrating our docs from the tikv Wiki to tikv.org. We should definitely let folks know if we achieve that.
I think we should also show the progress of backup/restore demo.
Plans for 4.0
can choose protobuf and prost?
We are already directing users to our new site for documentation. I think you can mention this in the Monthly.
Quote from Readme:
We are currently migrating our documentation from the TiKV's wiki page to the official website. We'd appreciate if you could check out the new look on the website and offer your feedback here. The Wiki page will be discontinued when the migration is finished. Stay tuned!
I want to have a section on 'interesting work in progress' I propose the following:
I want to check that all of this is ok to talk about publicly - @siddontang ?
I also don't know enough about the following to write anything:
I think we need only three sentences for each: what it is. Why it is awesome. Status/what is being worked on. Please can people write these for me?
titan and pessimistic transaction are not production-ready. although titan has been run in one big company for a long time, we still think we need to test it for some time before releasing it.
the previous backup is deprecated, and joint consensus has no any update.
so here, we can talk about RPN and follower/learner read.
titan and pessimistic transaction are not production-ready. although titan has been run in one big company for a long time, we still think we need to test it for some time before releasing it.
these sections are meant to describe work which is in-progress, not work which is finished, so the goals here are to make them production-ready, not assuming that they already are.
I think it is nice to talk about exciting work which is happening, even if there is not much progress.
@siddontang It's okay to talk about in development features, and titan was already released in 3.0 as stable.
maybe I should describe it as "improvements to ..." instead of "production-ready"
@nrc Follower/Learner Read (Maybe we shall call it Replica Read) enable TiKV to execute read command on Replicas. It can relieve the pressure of hot spot Leaders, accelerate read command execution when the client is far from Leader but is close to a Follower. It supports SI and linearizability in txn mode, but would hurt linearizability in raw mode. This function has already merged to TiKV master, can be enabled through an RPC option. We are working on supporting it in TiDB. Do I need to write a more detailed doc? :)
This month we supported the following function to be used in batch execution:
Closed - issue added
Comment if you have things that should be covered in this issue. Please leave a link.
Since this is the first issue, we should cover anything that has happened in the past few months.