[
https://issues.apache.org/jira/browse/IGNITE-19878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-19878:
-----------------------------------
Labels: ise (was: )
> Restrict possibility to create two caches with the same schema and index name
> -----------------------------------------------------------------------------
>
> Key: IGNITE-19878
> URL: https://issues.apache.org/jira/browse/IGNITE-19878
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.15
> Reporter: Evgeny Stanilovsky
> Assignee: Evgeny Stanilovsky
> Priority: Major
> Labels: ise
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> It’s possible to create two different caches with the same schema and index
> name inside it from a client and after that get a failing of the server node
> during start-up with the error "Duplicate index name... " during start caches.
> scenario:
> start at least two server nodes
> start client node which creates two different caches during start-up (via
> setting cache configs to config of client node) with the same schema name and
> index name, it leads to crushing the cluster
> then try to start the cluster and get the error "Duplicate index name..."
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
