Tried that as well and it worked, but it feels sub-optimal :)
Murtadha’s way also works nicely (and doesn’t require short reaction
times!) if you don’t want to be strictly in the RecoveryIT context.
Cheers,
Till
On 6 Nov 2015, at 17:04, Young-Seok Kim wrote:
I was doing what Ildar did and I did attaching quickly. :(
On Fri, Nov 6, 2015 at 4:34 PM, Till Westmann <[email protected]>
wrote:
Thanks for both replies!
@Ildar: When you added the JVM parameters for the CC or NC, how did
you go
about attaching at the “right” point in time? Did you stop the
JVM waiting
for the connection or were you “attaching quickly”?
Thanks again,
Till
On 5 Nov 2015, at 22:47, Murtadha Hubail wrote:
I think the easiest way without having to attach a remote debugger is
to
execute their queries manually in the web interface after running
AsterixHyracksIntegrationUtil in debugging mode. When it is time to
execute
kill_cc_nc.sh, just kill -9 the AsterixHyrackIntegrationUtil
process. Then
run AsterixHyrackIntegrationUtil again and it will perform the
recovery.
-Murtadha
On Nov 5, 2015, at 10:14 PM, Ildar Absalyamov
<[email protected]>
wrote:
Till,
The only way I found to debug it sometime ago when I needed was to
add
remote debugger into CC/NC JVM properties of
asterix-configuration.xml
(asterix-installer/src/main/resources/conf), which is used to setup
mini
cluster to tests.
On Nov 6, 2015, at 11:07, Till Westmann <[email protected]> wrote:
Hi,
I’m wondering how people go about running the code that is
executed by
one of the RecoveryIT in the debugger.
I imagine that there are number of ways to do that.
If you have done this at some point, could you describe how you
did
that?
Thanks,
Till
Best regards,
Ildar
