Hi Jason,
I agree with you that the user wanted to index all the data in the region when
using a partitioned region. But when the command is not successful, the cluster
config is not updated.
After the server restart, it will not have indexes as it is not stored in the
cluster configuration.
So
In case if you are planning to fix; the probable fix is not to send gfsh create
command to all the nodes when its partitioned region..
On 12/7/21, 6:37 AM, "Mario Kevo" wrote:
Hi Jason,
I agree with you that the user wanted to index all the data in the region
when using a partitioned
Are you thinking about not sending it to the remote nodes or not sending
requests from locator to the each node?
Also, there is one map where indexTask is stored, and there is putIfAbsent
method which seems is not working properly.
// This will return either the Index FutureTask or Index itself,
The IndexTask is working as expected...To handle multiple request creating the
same index.
It looks like, when there is multiple index creation request; It is handled
properly (using the Future task)
What is the case when it throws Index already exists?
The other option is if the index request m
Hi Mario!
I agree with you that the user wanted to index all the data in the region when
using a partitioned region. But when the command is not successful, the cluster
config is not updated.
After the server restart, it will not have indexes as it is not stored in the
cluster configuration.
Int
