Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug]: Encountered 'request is too large' error during binlog bulkinsert #39331

Open
1 task done
bigsheeper opened this issue Jan 16, 2025 · 0 comments
Open
1 task done

[Bug]: Encountered 'request is too large' error during binlog bulkinsert #39331

bigsheeper opened this issue Jan 16, 2025 · 0 comments
Assignees
@bigsheeper
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@bigsheeper
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: master&2.5&2.4
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

Image

Image

Expected Behavior

No response

Steps To Reproduce



Milvus Log


No response


Anything else?


No response

      		
    

      
  





        



            

              
            

        

      


      
    








      

    



      

  
            

    

      
    

    


      

          @bigsheeper
bigsheeper




            added
      

  kind/bug

  Issues or changes related a bug

      

  needs-triage

  Indicates an issue or PR lacks a `triage/foo` label and requires one.

  labels


      Jan 16, 2025

    

  



    

    

      
    

    


      

          @bigsheeper
bigsheeper




              self-assigned this


      Jan 16, 2025

    

  



  

  

    
  


  

      

  This was referenced Jan 16, 2025





  


  

      
   Open

  






      






  


  

      
   Merged

  






  




  


  
    
  
  

    
  sre-ci-robot 

      pushed a commit
      that referenced
      this issue

    
      Jan 17, 2025
    
    

      


  

    

      


  

      
        @bigsheeper
  





      

        
          enhance: [2.5] Limit the maximum number of segments restored and fail…
        

          
            
          

      


      

          

    
    
    

  

    


      


      

          

    
    
    

  

  

    
  



      


      
      

        
          b699942
        
      

    

  

    

      
… the job if saving the binlog fails (#39359)

1. Limit the maximum number of restored segments to 1024.
2. Fail the import job if saving binlog fails.
3. Fail the import job if saving the import task fails to prevent
repeatedly generating dirty importing segments.

issue: #39331

pr: #39344

Signed-off-by: bigsheeper <[email protected]>

    




    

  













  
  

    

      

  





  




  
  

              

  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment


  



  






  
                    




    

  


      
  

    Assignees
  



        

      

        

  
      @bigsheeper
  
    bigsheeper
    

      








      


  


  

    Labels
  



    

      

    kind/bug

  Issues or changes related a bug
  

    needs-triage

  Indicates an issue or PR lacks a `triage/foo` label and requires one.








      

  

    

        

    Projects
  


        




    None yet




  



      


  

    
  

    Milestone
  


      No milestone





    
      
          


  

    
      

        
    

    Development
  




          
    
No branches or pull requests







    
  




      

    

  
      

  

    

      1 participant
    

    

        
          @bigsheeper