geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jinmei Liao (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (GEODE-6772) create index sometimes will create the index but failed to update the cluster configuration.
Date Mon, 01 Jul 2019 15:28:00 GMT

    [ https://issues.apache.org/jira/browse/GEODE-6772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869670#comment-16869670
] 

Jinmei Liao edited comment on GEODE-6772 at 7/1/19 3:27 PM:
------------------------------------------------------------

[~mivanac] when a region is created via cache.xml, you have to use --member option to specify
which member has this region. With no --member option, gfsh assumes the region/index are managed
by cluster configuration.

It's generally acknowledged that if you mixed cache.xml with cluster configuration in gfsh,
there are bound to be some weird behaviors that are undocumented. It's recommended not to
mix cache.xml configuration with cluster configuration


was (Author: jinmeiliao):
[~mivanac] when a region is created via cache.xml, you have to use --member option to specify
which member has this region. With no --member option, gfsh assumes the region/index are managed
by cluster configuration.

> create index sometimes will create the index but failed to update the cluster configuration.
> --------------------------------------------------------------------------------------------
>
>                 Key: GEODE-6772
>                 URL: https://issues.apache.org/jira/browse/GEODE-6772
>             Project: Geode
>          Issue Type: Bug
>          Components: gfsh, management
>            Reporter: Jinmei Liao
>            Assignee: Jinmei Liao
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Scenario:
> 1. start a server (server-1) in group1: start server --name=server-1 --group=group1
> 2. start another server-2 with no group: start server --name=server-2
> 3. create a regionA in group1: create region --name=regionA --group=group1 --type=REPLICATE
> 4. create an index on regionA: create index --region=regionA  --name=index1 ....
> observe that command will try to create index on both servers, but failed on server-2,
since server-2 has no regionA, but the failure caused the cluster configuration not being
updated.
> Proposal:
> when create index, the region already should determine what members this  index needs
to be created on, there should be no need for user to specify a group. We should ignore "group"
when cluster configuration is enabled.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message