I'm not sure if it's the exact same issue, but I have observed the replication
failing under heavy load where the replication buffers would fill faster than
the logs can be shipped to the slave (even with fast servers & fast network).
I've previously tweaked a copy of derby to allow up to 100 buf
have blob
tables with large image files, and I'm measuring end-to-end delete (from web
browser application to server and back) at around 100 ms.
-geoff
“XML? Too much like HTML. It'll never work on the Web!”
-anonymous
____
From: Andrew Lawrenson
T
Hi,
I've been experiencing a performance problem with deleting blobs in derby, and
was wondering if anyone could offer any advice.
This is primarily with 10.4.2.0 under windows and solaris, although I've also
tested with the new 10.5.1.1 release candidate (as it has many lob changes),
but this
Knut,
I can't see a JIRA issue raised by anyone for this, so I've raised one
(https://issues.apache.org/jira/browse/DERBY-3927)
Andy
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 22 October 2008 12:29
To: Derby Discussion
Subject: Re: replica
ons due to being a slave - but this is about the only
programatic check I've come up with so far.
Andrew Lawrenson
-Original Message-
From: Glenn McGregor [mailto:[EMAIL PROTECTED]
Sent: 21 October 2008 23:18
To: Derby Discussion
Subject: Re: replication - master log overflow
Jørgen L
hing back after failover
Andrew Lawrenson <[EMAIL PROTECTED]> writes:
> Jorgen/Knut,
>
> many thanks for this.
>
> one clarification - "should" it work in the scenario where on
> the master you do a restore from the slave & roll forward
> through the logs?
many thanks,
Andrew.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 14 October 2008 12:43
To: Derby Discussion
Subject: Re: Replication - switching back after failover
Knut Anders Hatlen wrote:
> Andrew Lawrenson <[EMAIL PROTECTED]> writes:
>> (.
whether you do a straight binary copy of the slave database, versus
doing a restore? (which should create a logically identical database, but may
not be the same exact binary files).
many thanks in advance for any advice,
Andrew Lawrenson
lized somewhere else than through SlaveController.
Regards,
Jørgen Løland
Andrew Lawrenson wrote:
> Jorgen,
>
> I've possibly found where the problem is being caused. (This
> is with v 10.4.2.0)
>
> When booting my slave database, a nullpointer exception is being thrown
ctFactory);
The comments here imply the order has to be this way round - however, it seems
to be this ordering which is causing the problem in my case.
At this point, I'm starting to feel quite out of my depth - does this make
sense to you?
Thanks again,
Andy
-----Original Messa
ations
6: Master: connect 'jdbc:derby:enctest2;failover=true';
7: Slave: connect
'jdbc:derby:enctest2;encryptionAlgorithm=DES/CBC/NoPadding;encryptionKey=test';
8. Slave: ensure results are as expected
Hope this helps,
Jørgen Løland
Andrew Lawrenson wrote:
> Hi All,
>
>
m I doing something wrong? Or is this assertion not
really valid when using replication? Any advice?
many thanks in advance,
Andrew Lawrenson
:185)
Is it possible for anyone to confirm if this should be supported or not?
many thanks,
Andrew Lawrenson
Many thanks for confirming this.
Andrew Lawrenson.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 16 September 2008 13:00
To: Derby Discussion
Subject: Re: Stopping & (Re)Starting Slave within replication
Hi Andrew,
Replication should not fail
ax.net.DefaultServerSocketFactory.createServerSocket(ServerSocketFactory.java:169)
at
org.apache.derby.impl.store.replication.net.ReplicationMessageReceive$2.run(Unknown
Source)
... 21 more
Is this something that ought to work? - or in this scenario would I need to
restart derby completely?
many thanks in advance for any advice.
Andrew Lawrenson
What's worked for me (although anyone else feel free to correct me) is:
1) checkpoint the database by running SYSCS_UTIL.SYSCS_CHECKPOINT_DATABASE()
2) freeze the database by running SYSCS_UTIL.SYSCS_FREEZE_DATABASE()
3) copy your log files (_all_ files in log dir)
4) unfreeze the database by runn
the wrong list to be asking - should I pose this on
derby-developers instead?
Many thanks,
Andrew Lawrenson
-Original Message-
From: Andrew Lawrenson [mailto:[EMAIL PROTECTED]
Sent: 29 February 2008 14:56
To: Derby Discussion
Subject: RE: Derby, identity columns & loc
mething I just have to live with, or is it an issue? Any
potential workarounds that don't involve replacing identity columns with GUIDs
or similar?
thanks in advance,
Andrew Lawrenson
-Original Message-
From: Andrew Lawrenson [mailto:[EMAIL PROTECTED]
Sent: 2
|
Many thanks,
Andrew Lawrenson
19 matches
Mail list logo
