Skip to main content

ReflexiveMoveout configuration parameter

  • January 21, 2017
  • 3 replies
  • 18 views
caliskurahmet

Hello, 

 

I would like to know what is the usage of this ReflexiveMoveout parameter? We have 12 nodes  version 7.2.3-10 vertica   and one of the nodes's WOS keeps getting full (16GB) and starts doing WOS_SPILL which looks like it impacts whole cluster's performance. Even though i decreased both MoveOutInterval (200) and MoveOutMaxAgeTime(900) , we're still seeing one node doing too many WOS_SPILL . For permenant solution we may need to check segmentation of projections but for short term solution , I'm trying to optimize mouveou and mergeout intervals . I was looking for detailed ReflexiveMoveout  explanation but could not find on documentation.Could you please give examples of use case of this parameter please ?

 

Thanks

 

 

    3 replies

    SruthiA
    Forum|alt.badge.img+1
    • SruthiA
    • Participating Frequently
    • January 23, 2017

    Are you doing trickle loading? Do you use DIRECT keyword when loading data? 

    caliskurahmet
    • caliskurahmet
    • Author
    • New Participant
    • January 26, 2017

    Hello ,

     

    We're using both trickle and direct loading , we found our problem is TM moveout is delayed because  some open sessions(SELECT 1) coming from our report servers  holding Global Catalog X lock . I would still like to learn use cases of enabling ReflexiveMoveout parameter, I could not find any explanation for how does that parameter work.

    Forum|alt.badge.img+2
    • Anonymous
    • Participating Frequently
    • January 31, 2017

    I also recomend you check following knowledge base document on tuple mover. It does not talk about reflexiveMoveout but has useful information to solve your problem.

    https://community.dev.hpe.com/t5/Vertica-Knowledge-Base/Tuple-Mover-Best-Practices/ta-p/235261

    Still scrolling?
    Ask a question
    Terms & ConditionsAccessibility statement