This post is more than 5 years old
14 Posts
0
2680
December 23rd, 2011 05:00
Event based retention (Failed to commit XSet: = -10158) anomaly
Hi, I just have encountered a weird anomaly with our in-house centera servers.
I have implemented a feature for saving files with event based retention (this is the core requirement) and it can be set at any time (during creation, or after creation)
When I tested my implementation on EMC test clusters, my solution worked correctly, however with our in-house servers I have encountered an error when doing commit (Failed to commit XSet: = -10158).
Now what is even worse than that, is that once I get this error, every other test case fails with other errors. Test cases are executed as one-by-one as usual, so it seems this error has an impact on server stability ! If i run these test cases again, but without running the first one, they work.
The code itself works this way (just simplified)
- Connect with centera server
- Write field with string value - just for verify it later
- Create retention policy "event"
- Set enabled flag
- Set duration
- Specify retention start
- Commit xset - FAILS!
Anyone has any clue what is going on ?
mckeown_paul
409 Posts
0
December 28th, 2011 08:00
You need to purchase an Advanced Retention License and then install the licence on you Centera cluster. The cluster as you say also need to be running GE as a minimum. As Mike says the fact that retention hold is marked as false would indicate that you don't have the licence installed and/or cluster is not in GE mode.
mfh2
208 Posts
0
December 23rd, 2011 12:00
Hi Dmitri -
Are your in-house Centeras running an up-to-date version of CentraStar? XAM requires version 4.0.1 or later to function correctly.
Regards,
Mike Horgan
DmitriKuznetsoi
14 Posts
0
December 27th, 2011 03:00
Hi, is that value can be obtained from "com.emc.centera.poolinfo.version" field ?
Here is a brief snapshot of cluster details that I have managed to gather:
System time: 27.12.2011 13:00:09
Authenticated: True
Auto delete: False
Running queries commit: False
Continue when disconnected: False
Max fields: 9223372036854775807
Max stream size: 107374182400
Query level 1: True
Query level 2: False
Shred: False
EMC specific:
EMC - VIM version:1.0.103
EMC - Cluster name:centera
EMC - Pool info version:4.1.1-3839-3-0
EMC - Max connections:100
EMC - Compliance retention-hold:unsupported
EMC - Retention default:0
EMC - Retention fixed minimum:0
EMC - Retention fixed maximum:-1
EMC - Retention variable minimum:0
EMC - Retention variable maximum:-1
EMC - Retention hold allowed:false
EMC - Retention hold pools:
mfh2
208 Posts
1
December 27th, 2011 04:00
Yes, the version looks OK. The retention hold allowed = false makes me think your Centera may not have an advanced retention license installed? Unfortunately, I do not recall how to check this, perhaps someone from EMC could comment.
Good Luck,
Mike Horgan
DmitriKuznetsoi
14 Posts
0
December 27th, 2011 04:00
Thank you!
This was also suspicious to me, it seems that this advanced retention is available only starting from "Centera Governance Edition"
So far I cannot verify if it is the case.
I would like to get a feedback from someone working at EMC on this topic, please.
DmitriKuznetsoi
14 Posts
0
December 29th, 2011 02:00
Thank you, it is clear now.
We are going to obtain required licenses then.