Error in markForCollection

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Error in markForCollection

hernan.wilkinson
Hi,
 I'm running a markForCollection in a extent that only has the topaz and basic gems running and I get this error:

Errors were found in execution:
-----------------------------------------------------
GemStone: Error         Nonfatal
Garbage collection aborted, reason: 'gcLock denied, vote state 1 =
voting, 02/22/2010 06:31:59 PM EST', conflict code:  --- .  Garbage
collection was aborted and should be tried again later.
Error Category: [GemStone] Number: 3006 Arg Count: 1
Arg 1: gcLock denied, vote state 1 = voting, 02/22/2010 06:31:59 PM EST

When I stopped all gc gems, it worked...
The problem is that on running stone (with swazoo running), I can not make a markForCollection becuase I get the same error... is it there that I'm forgetting to do before running the mark?

 Thanks
 Hernan.
Reply | Threaded
Open this post in threaded view
|

Re: Error in markForCollection

Dale
Hernan,

You shouldn't have to shut down the gc gems to do an MFC. I don't have the code handy to look at the conditions where the gc gems will hold onto the lock, but I'd guess that the lock is being held onto by one or more gc gems while they are doing an operation ...

I'll try to find out more details tomorrow (unless someone else answers first)...

Dale
----- "Hernan Wilkinson" <[hidden email]> wrote:

| Hi,
|  I'm running a markForCollection in a extent that only has the topaz
| and
| basic gems running and I get this error:
|
| Errors were found in execution:
| -----------------------------------------------------
| GemStone: Error         Nonfatal
| Garbage collection aborted, reason: 'gcLock denied, vote state 1 =
| voting, 02/22/2010 06:31:59 PM EST', conflict code:  --- .  Garbage
| collection was aborted and should be tried again later.
| Error Category: [GemStone] Number: 3006 Arg Count: 1
| Arg 1: gcLock denied, vote state 1 = voting, 02/22/2010 06:31:59 PM
| EST
|
| When I stopped all gc gems, it worked...
| The problem is that on running stone (with swazoo running), I can not
| make a
| markForCollection becuase I get the same error... is it there that
| I'm
| forgetting to do before running the mark?
|
|  Thanks
|  Hernan.
Reply | Threaded
Open this post in threaded view
|

Re: Error in markForCollection

otto
Hi,

The strategy that we follow is to wait for an epoch to finish and then
sneak an MFC in before another one starts. You must not shut down gc
gems.

Check that your epochs are not too close together. If so, you'll not
get a chance.

Ensure that voting time is as small as possible by stopping sessions
that could hold up the voting. (Ones that are too busy with things to
vote.) stopUserSessions may help.

Here's what we do in our MFC script for GS 32 bit. Now this is quite
ugly, I know, but it works.

Parse the most recent <stone name>gcepc.log file. Look for "epochGcs".
If you have "epochGcs" at the bottom of the file (and not "final
possible dead size"), don't start an MFC. As soon as "final possible
dead size" appears in the log, start an MFC.

I see that the log <stone name>_<pid>admingcgem.log contains useful
info in GS 64 bit. I see "Starting doSweepWsUnion" and then "Finished
sweeping possible dead" at the end. Perhaps this is the way for GS 64
bit?

My 2 cents.

Cheers
Otto



On Tue, Feb 23, 2010 at 4:51 AM, Dale Henrichs
<[hidden email]> wrote:

> Hernan,
>
> You shouldn't have to shut down the gc gems to do an MFC. I don't have the code handy to look at the conditions where the gc gems will hold onto the lock, but I'd guess that the lock is being held onto by one or more gc gems while they are doing an operation ...
>
> I'll try to find out more details tomorrow (unless someone else answers first)...
>
> Dale
> ----- "Hernan Wilkinson" <[hidden email]> wrote:
>
> | Hi,
> |  I'm running a markForCollection in a extent that only has the topaz
> | and
> | basic gems running and I get this error:
> |
> | Errors were found in execution:
> | -----------------------------------------------------
> | GemStone: Error         Nonfatal
> | Garbage collection aborted, reason: 'gcLock denied, vote state 1 =
> | voting, 02/22/2010 06:31:59 PM EST', conflict code:  --- .  Garbage
> | collection was aborted and should be tried again later.
> | Error Category: [GemStone] Number: 3006 Arg Count: 1
> | Arg 1: gcLock denied, vote state 1 = voting, 02/22/2010 06:31:59 PM
> | EST
> |
> | When I stopped all gc gems, it worked...
> | The problem is that on running stone (with swazoo running), I can not
> | make a
> | markForCollection becuase I get the same error... is it there that
> | I'm
> | forgetting to do before running the mark?
> |
> |  Thanks
> |  Hernan.
>
Reply | Threaded
Open this post in threaded view
|

Re: Error in markForCollection

hernan.wilkinson
thanks Otto... it is a petty the error does not say the gem that is not voting...

On Tue, Feb 23, 2010 at 8:26 AM, Otto Behrens <[hidden email]> wrote:
Hi,

The strategy that we follow is to wait for an epoch to finish and then
sneak an MFC in before another one starts. You must not shut down gc
gems.

Check that your epochs are not too close together. If so, you'll not
get a chance.

Ensure that voting time is as small as possible by stopping sessions
that could hold up the voting. (Ones that are too busy with things to
vote.) stopUserSessions may help.

Here's what we do in our MFC script for GS 32 bit. Now this is quite
ugly, I know, but it works.

Parse the most recent <stone name>gcepc.log file. Look for "epochGcs".
If you have "epochGcs" at the bottom of the file (and not "final
possible dead size"), don't start an MFC. As soon as "final possible
dead size" appears in the log, start an MFC.

I see that the log <stone name>_<pid>admingcgem.log contains useful
info in GS 64 bit. I see "Starting doSweepWsUnion" and then "Finished
sweeping possible dead" at the end. Perhaps this is the way for GS 64
bit?

My 2 cents.

Cheers
Otto



On Tue, Feb 23, 2010 at 4:51 AM, Dale Henrichs
<[hidden email]> wrote:
> Hernan,
>
> You shouldn't have to shut down the gc gems to do an MFC. I don't have the code handy to look at the conditions where the gc gems will hold onto the lock, but I'd guess that the lock is being held onto by one or more gc gems while they are doing an operation ...
>
> I'll try to find out more details tomorrow (unless someone else answers first)...
>
> Dale
> ----- "Hernan Wilkinson" <[hidden email]> wrote:
>
> | Hi,
> |  I'm running a markForCollection in a extent that only has the topaz
> | and
> | basic gems running and I get this error:
> |
> | Errors were found in execution:
> | -----------------------------------------------------
> | GemStone: Error         Nonfatal
> | Garbage collection aborted, reason: 'gcLock denied, vote state 1 =
> | voting, 02/22/2010 06:31:59 PM EST', conflict code:  --- .  Garbage
> | collection was aborted and should be tried again later.
> | Error Category: [GemStone] Number: 3006 Arg Count: 1
> | Arg 1: gcLock denied, vote state 1 = voting, 02/22/2010 06:31:59 PM
> | EST
> |
> | When I stopped all gc gems, it worked...
> | The problem is that on running stone (with swazoo running), I can not
> | make a
> | markForCollection becuase I get the same error... is it there that
> | I'm
> | forgetting to do before running the mark?
> |
> |  Thanks
> |  Hernan.
>