[
http://jira.amdatu.org/jira/browse/AMDATU-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivo Ladage - van Doorn updated AMDATU-318:
------------------------------------------
Description:
First setup a Cassandra cluster as described in this use case:
http://www.amdatu.org/confluence/display/Amdatu/Use+case+2
Assume that node A is the seed (master) of node B.
Now to reproduce:
- Open dashboards of node A and B, login as Administrator and add UserAdmin
gadget
- Add a user '01' on node A (using UserAdmin gagdet), note that it appears on
node B
- Stop node B
- Create another user '02' on node A
- Remove user '01' on node A
- Start node B
Now note that user '02' is now available on node B, but also user '01' is still
present, which should have been removed (upon Hinted handoff and read repair).
Also tried removing the users using cassandra-cli instead, but the result is
the same.
was:
First setup a Cassandra cluster as described in this use case:
http://www.amdatu.org/confluence/display/Amdatu/Use+case+2
Assume that node A is the seed (master) of node B.
Now to reproduce:
- Open dashboards of node A and B, login as Administrator and add UserAdmin
gadget
- Add a user '01' on node A, note that it appears on node B
- Stop node B
- Create another user '02' on node A
- Remove user '01' on node A
- Start node B
Now note that user '02' is now available on node B, but also user '01' is still
present, which should have been removed (upon Hinted handoff and read repair).
> Tombstones out of sync on node B in Cassandra cluster when they are removed
> from node A during downtime of node B
> -----------------------------------------------------------------------------------------------------------------
>
> Key: AMDATU-318
> URL: http://jira.amdatu.org/jira/browse/AMDATU-318
> Project: Amdatu
> Issue Type: Bug
> Components: Amdatu Cassandra
> Affects Versions: 0.2.0
> Reporter: Ivo Ladage - van Doorn
> Fix For: 0.2.0
>
>
> First setup a Cassandra cluster as described in this use case:
> http://www.amdatu.org/confluence/display/Amdatu/Use+case+2
> Assume that node A is the seed (master) of node B.
> Now to reproduce:
> - Open dashboards of node A and B, login as Administrator and add UserAdmin
> gadget
> - Add a user '01' on node A (using UserAdmin gagdet), note that it appears on
> node B
> - Stop node B
> - Create another user '02' on node A
> - Remove user '01' on node A
> - Start node B
> Now note that user '02' is now available on node B, but also user '01' is
> still present, which should have been removed (upon Hinted handoff and read
> repair).
> Also tried removing the users using cassandra-cli instead, but the result is
> the same.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
