Management Console and KSAFE

When I run a manual DBD from Vertica Management Console ( only build/not deploy automatically ) , the resulting script always defaults to ksafe 0

( 1st and last line in resulting script : select mark_design_ksafe(0); )

I always select ksafe 1 in the general tab

We got a 3 node cluster and the ksafe level is 1 ( vertica 7.1.12 )  

Has anyone observed this behaviour before ?  Or can someone tell me what is wrong ?

Thanks

 

Comments

  • SruthiASruthiA Vertica Employee Administrator

    Hi Karin,

     

        When you select to run manual DBD, it gives you a summary of design before saving it. By default KSafety is set to  0 there. DId you change it to 1 before building it?

     

     

    -Regards,

     Sruthi

  • Hi SruthiA 

    Yes I did select ksafe 1 before building the DBD , but it seems to be ignored and I cannot see the reason why

    When I first saw the output ( i.e. first line:  select mark_design_ksafe(0); ) I thought indeed, that I had forgotten to select it on the general tab, but then I created a new manual design and made certain, that I clicked it .... yet ksafe= 0 in the resulting output

    I do understand, that you do not encounter the same problem ?

    Thank you for yoy reply

  • SruthiASruthiA Vertica Employee Administrator

    Hi,

     

      Can you share me the output of rpm -qa|grep vertica and the script generated from DBD?

     

     

    -Regards,

     Sruthi

  • Hi Sruthi

    Of course, I've uploaded both

  • Hi Sruthi

    Of course, I've uploaded both ( apparently I've uploaded them twice :) )

     

  • SruthiASruthiA Vertica Employee Administrator

    Hi,

     

      Can you share me the output of the following queries

     

    1) select * from nodes;

    2) select * from system;

     

    -Regards,

     Sruthi

  • Hi Sruthi

    I've added both results ( nodes and system ) to the excel wb attached

    Thanks for your help

     

  • SruthiASruthiA Vertica Employee Administrator

    Hi,

     

       I checked your script and it looks like buddy projections are not created for the two tables properly. In order to confirm regarding it can you execute the following the query

     

    SELECT MARK_DESIGN_KSAFE(1);

    select * from projections where anchor_table_name ilike '%iXR_cdf_events%';

     

     

    -Regards,

     Sruthi

  • Hi Sruthi

    Indeed I nearly executed the script straight away...but I then noticed the ksafe setting and therefore manually altered it ( leaving the current ksafe level  and setting ksafe 1 on create projection statement, and I think you saw that already in the output from systems - current fault tolerance = 1 )

    So, projections currently are : ( pls see attachement )

     

  • SruthiASruthiA Vertica Employee Administrator

    Hi,

     

       I reproduced your case in my environment. There are only scenarios in which statement "select mark_design_ksafe(0);" is added to the design script built from Management Console

     

    1) if K-Safe is set to 1 in the database, but when we forget to change the option of K-Safety to 1 before building the design in MC

    2) if the projection definitions do not meet K-safe design requirements. 

     

     

    -Regards,

     Sruthi 

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file