Ivan,
This issue doesn't seem to be a blocker for 2.8 release from my point of view. I think we definitely will have such bugs in future and 2.8.1 is our goal for them. Please, let me know if we should wait for the fix and include it exactly in 2.8. On Fri, 28 Feb 2020 at 15:40, Nikolay Izhikov <[email protected]> wrote: > > Igniters, > > I think we can replace cache name with the cache id. > This should solve issue with the length limitation. > > What do you think? > > > 28 февр. 2020 г., в 15:32, Ivan Bessonov <[email protected]> написал(а): > > > > Hello Igniters, > > > > we have an issue in master branch and in the upcoming 2.8 release that > > related to new metrics functionality implemented in [1]. You can't use new > > "configureHistogramMetric" and "configureHitRateMetric" configuration > > methods on caches with long names. My estimation shows that cache with 30 > > characters in its name will shut down your whole cluster with failure > > handler if > > you try to change metrics configuration for it using one of those methods. > > > > Initially we wanted to merge [2] to show a valid error message instead of > > failing > > the cluster, but it wasn't in plans for 2.8 because we didn't know that it > > clashes > > with [1]. > > > > I created issue [3] with plans of removing MetaStorage key length > > limitations, but > > it requires some thoughtful MetaStorageTree reworkings. I mean that it > > can't be > > done in only a few days. > > > > What do you think? Does this issue affect 2.8 release? AFAIK new metrics are > > experimental and they can have some known issues. Feel free to ask me for > > more > > details if it's needed. > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-11987 > > [2] https://issues.apache.org/jira/browse/IGNITE-12721 > > [3] https://issues.apache.org/jira/browse/IGNITE-12726 > > > > -- > > Sincerely yours, > > Ivan Bessonov >
